On Mon, 11 Dec 2000 stewart@neuron.com wrote:
>
> very helpful.
>
> Technical merits and voter intent aside, this behavior is misleading and
> inconsistent with previous kernels. Tools like top or a CPU dock applet show
> a constantly loaded CPU. Hacking them to deduct the load from 'kapm-idled'
> seems like the wrong answer.
>
> stewart
>
Err.. Did you see the comment about shared memory info being permanently
removed because (something about too CPU intensive to justify...)?
It looks like we need to find another way to get kernel info rather
than from /proc. We need to calculate stuff only when it's needed.
Calculating stuff all the time, to make it available should somebody
care to read it in the /proc file-system is wasteful.
Maybe we need to have some kind of 'kernel ioctl' where a user-mode caller
'pays' for the CPU cycles necessary to obtain the info that the caller
requests. A better idea might be to have the 'read' of a particular
/proc file-system item, result in the calculation of the new values.
That way, the read and calculation of new values gets charged to
the reader.
In any event, the continuous calculation of 'kernel stuff' that may
be read once a week at most, is definitely a waste of CPU cycles.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.0 on an i686 machine (799.54 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Dec 15 2000 - 21:00:22 EST