The message quoted below is from a MandrakeSoft co-worker and friend, in
a thread discussing APM's kernel thread, and how the idle function uses
CPU time. This thread was in response to yet another Bugzilla bug
report about kapm-idled using CPU time.
Several months ago, kapmd was renamed to kapm-idled in an attempt to
signal users that it was a special process, and that its CPU time wasn't
"real CPU time." This hasn't silenced the bug reports and confusion.
Is there some way to hack the scheduler statistics so that idle
processes are special cases, which do not accumulate CPU time nor
contribute to the load average?
I agree that it's not pretty to special case idle function process(es),
but those idle functions in turn are causing an incorrect picture of the
system state to be presented to userland.
Jeff
-- Jeff Garzik | May you have warm words on a cold evening, Building 1024 | a full mooon on a dark night, MandrakeSoft | and a smooth road all the way to your door.Guillaume Cottenceau wrote: > On the other hand, you'll agree Jeff that it needs some fixing: it's > fucking up many statistics such as load average and instant cpu usage, and > is very confusing for people.. > > On another side, what I don't understand is that its cpu usage is not > constant, which makes people things it's sort of a bug: for example my > machine is up 1 day, 18:33 with 2.4.2-15mdk, kapm-ideld is reported to > have consumed 1355m, but currently it's staying at 0.0% of cpu. Sometimes > it gets bigger, sometimes it gets lower. Rather confusing. - 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/
This archive was generated by hypermail 2b29 : Fri Mar 23 2001 - 21:00:11 EST