Re: Incorrect CPU process accounting using CONFIG_HZ=100

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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Incorrect CPU process accounting using CONFIG_HZ=100
  - From: Pavel Machek <[email protected]>

References:
- Incorrect CPU process accounting using CONFIG_HZ=100
  - From: Al Boldi <[email protected]>
- Re: Incorrect CPU process accounting using CONFIG_HZ=100
  - From: Jan Engelhardt <[email protected]>

Prev by Date: Re: [PATCH] drm: Add VIA chipset IDs for drm detection
Next by Date: Re: CONFIG_VGACON_SOFT_SCROLLBACK crashes 2.6.17
Previous by thread: Re: Incorrect CPU process accounting using CONFIG_HZ=100
Next by thread: Re: Incorrect CPU process accounting using CONFIG_HZ=100
Index(es):
- Date
- Thread

[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]