Roger Luethi writes:

quoted

Most of the current problems with proc are related to tools: They don't
like changes and some of them are very sensitive to resource usage
(because they may make hundreds of calls per second on typical systems).

On Fri, Aug 06, 2004 at 10:02:28AM -0400, Albert Cahalan wrote:

Make that 2000 /proc reads per second or more. This is too slow.
I need to read about 1 million /proc files per second.

This is a truly terrifying prospect. The vfs overheads of manipulating
that much metadata is unthinkably enormous, not to mention the very
real tasklist_lock starvation issues killing boxen dead now.

By any chance could a rate-limited incremental algorithm be used,
at least for top(1)?


-- wli
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>