On Wed, 31 Jul 2002, Benjamin LaHaise wrote:

Why?  Filling the entire ram with dirty pages is okay, and in fact you
want to support that behaviour for apps that "just fit" (think big
scientific apps).  The only interesting point is that when you hit the
limit of available memory, the system needs to block on *any* io
completing and resulting in clean memory (which is reasonably low
latency), not a specific io which may have very high latency.

Also, the system shouldn't try writing out the complete inactive
list at once and blocking in __get_request_wait instead of grabbing
pages as they become cleaned.

regards,

Rik
-- 
Bravely reimplemented by the knights who say "NIH".

http://www.surriel.com/		http://distro.conectiva.com/

--
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/