From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Chris Frey <cdfrey@foursquare.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM policy, overcommit control, and soft limits
Date: Sat, 31 May 2008 14:15:29 +0100 [thread overview]
Message-ID: <20080531141529.2a5c085a@core> (raw)
In-Reply-To: <20080531102752.GA25244@foursquare.net>
> I'm sure someone has thought of this before me. Does anything remotely
> similar to this already exist? I've googled for OOM policy, but so far
> all I've seen is Rusty Lynch's patch from 2003, and really, I want this
> behaviour to happen when there is still a bit of memory left, so things
> can be dealt with before they are OOM-level dire.
Not that I am aware of. However you can set priorities on OOM killing
order and there is a patch from the XO people which seems to have
vanished into the darkness which added a nice memory pressure notifier so
apps could respond to memory shortages intelligently (eg by cleaning up)
next prev parent reply other threads:[~2008-05-31 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 10:27 OOM policy, overcommit control, and soft limits Chris Frey
2008-05-31 13:15 ` Alan Cox [this message]
2008-05-31 16:41 ` Andrea Righi
[not found] <azwvH-5QW-5@gated-at.bofh.it>
2008-05-31 12:48 ` Alan Jenkins
2008-05-31 15:23 ` Alan Cox
2008-05-31 16:45 ` Alan Jenkins
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=20080531141529.2a5c085a@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cdfrey@foursquare.net \
--cc=linux-kernel@vger.kernel.org \
/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