> 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.
And instrumenting the number of calls to the apm idle function I am
not convinc
On Sun, 18 Mar 2001, Jeff Garzik wrote:
> 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?
It's trivial. I remember seeing a patch that does exactly this
on linux-kernel, probably
[EMAIL PROTECTED] (Jeff Garzik) writes:
> 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 wondered about getting kapm-idled to take the CPU time allocated to
itself, and realloc
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
4 matches
Mail list logo
