From: Mike S <wickedchicken@plasticpenguins.com>
To: Robert Love <rml@tech9.net>
Cc: Jamie Lokier <jamie@shareable.org>,
rusty@linux.co.intel.com, riel@conectiva.com.br,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Enabling other oom schemes
Date: Sun, 14 Sep 2003 20:11:43 -0400 [thread overview]
Message-ID: <3F6503BF.405@plasticpenguins.com> (raw)
In-Reply-To: <1063476152.24473.30.camel@localhost>
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>
prev parent reply other threads:[~2003-09-15 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 2:19 Rusty Lynch
2003-09-12 4:18 ` Rahul Karnik
2003-09-12 4:31 ` Chris Friesen
2003-09-12 4:40 ` Rahul Karnik
2003-09-12 4:48 ` Robert Love
2003-09-12 11:18 ` Helge Hafting
2003-09-12 14:07 ` Chris Friesen
2003-09-12 14:30 ` M. Edward Borasky
2003-09-12 4:47 ` Robert Love
2003-09-13 17:48 ` Jamie Lokier
2003-09-13 20:52 ` Robert Love
2003-09-14 5:28 ` Chris Friesen
2003-09-15 0:11 ` Mike S [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F6503BF.405@plasticpenguins.com \
--to=wickedchicken@plasticpenguins.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=rml@tech9.net \
--cc=rusty@linux.co.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox