<<<<<<<<<<<<<<<<<<
10032 processes: 10030 sleeping, 1 running, 1 zombie, 0 stopped
CPU states: 1.3% user, 101.4% system, 0.0% nice, 0.0% idle
Mem: 969692K av, 420244K used, 549448K free, 2212064K shrd, 3268K
buff
Swap: 130748K av, 0K used, 130748K free 7640K
cached
>>>>>>>>>>>>>>>>>>
Yeah, the "top" command is slow....
My proposal is to generalize the idea of /proc/sys/kernel/max-threads,
even if the ingo's patch is not applied.
It is great and may allow to write (at last) a dynamic "top" commmand
that would open the /proc/sys/kernel/max-threads, read the value and
malloc the required space.
Of course, echo "xxxxx" >/proc/sys/kernel/max-threads has to be refused.
Do you agree? I'm ready to update top command but unable to modify
the kernel to support the /proc/sys/kernel/max-threads. Volunteers?
-- *--* mailto:Jean-Michel.Vansteene@bull.net (Bull) *--* mailto:vanstee@worldnet.fr (Home) *--* http://www.worldnet.fr/~vanstee (Jean GABIN) ------------------------------------------------------------- - - - - - U n L i n u x s i n o n r i e n - - - - - - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/