> 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.
That is not so great. People will want to change that value on a
running system if it is variable. (otherwise, 100000 is good)
> 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?
If you do that, please start from the most recent version:
http://www.cs.uml.edu/~acahalan/linux/procps-981104.tar.gz
For everybody: please download and test that.
-
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/