lkml.org 
[lkml]   [2006]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Incorrect CPU process accounting using CONFIG_HZ=100
Date
Jan Engelhardt wrote:
> >Setting CONFIG_HZ=100 results in incorrect CPU process accounting.
> >
> >This can be seen running top d.1, that shows top, itself, consuming 0ms
> >CPUtime.
> >
> >Will this bug have consequences for sched.c?
>
> Works for me, somewhat.
> TIME+ says 0:00.02 after 70 secs. (Ergo: top is not expensive on this
> CPU.)

That's what I thought for a long time. But at closer inspection, top d.1
slows down other apps by about the same amount of time at 1000Hz and 100Hz,
only at 1000Hz it is accounted for whereas at 100Hz it is not.

Thanks!

--
Al

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-06-22 19:39    [W:0.941 / U:0.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site