On Thu 2006-06-22 20:36:39, Al Boldi wrote:
> 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.
It is not a bug... it is design decision. If you eat "too little" cpu
time, you'll be accouted 0 msec. That's what happens at 100Hz...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
