Re: Incorrect CPU process accounting using CONFIG_HZ=100

>
>
>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.)

>Thanks!

Jan Engelhardt
-- 
-
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: Al Boldi <[email protected]>

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

Prev by Date: Re: Areca driver recap + status
Next by Date: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
Previous by thread: 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]