Robert Love wrote:

One thing to keep in mind is that during a real OOM condition, we cannot
allocate _any_ memory.  None. Zilch.

And that makes some things very hard.  When we start getting into things
such as complicated policies that kill nonessential services first, et
cetera... there comes a time where a lot of communication is needed
(probably with user-space).  Hard to do that with no memory.

A possible, but not very efficient workaround is to reserve memory or 
swap just for this condition. Obviously this limits available memory for 
other process (which in theory could cause an OOM in the first place) 
and would be wasted most of the time. Possibly this reserved memory 
would be used as a filesystem read cache until OOM, when it would be 
cleared out and used for whatever.

-- 

~Mike
wickedchicken@plasticpenguins.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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>