lkml.org 
[lkml]   [2003]   [Sep]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] Enabling other oom schemes
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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:48    [from the cache]
©2003-2011 Jasper Spaans