From: Andrea Righi <righi.andrea@gmail.com>
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 18:41:18 +0200 [thread overview]
Message-ID: <48417FAE.7040103@gmail.com> (raw)
In-Reply-To: <20080531102752.GA25244@foursquare.net>
Chris Frey wrote:
> 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.
Have you seen the OOM killer policy implemented in memory the resource
controller?
http://kernelnewbies.org/Linux_2_6_25#head-450b26e12955b8035a05cf07b3f31c501ee4bfab
BTW read the TODO comment in this commit log... ;-)
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c7ba5c9e8176704bfac0729875fa62798037584d
Maybe a possible solution could be to just run critical and non-critical
applications in 2 different cgroups, using different memory policies.
Anyway, userspace OOM handling would surely permit to implement more
interesting features.
-Andrea
next prev parent reply other threads:[~2008-05-31 16:41 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
2008-05-31 16:41 ` Andrea Righi [this message]
[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=48417FAE.7040103@gmail.com \
--to=righi.andrea@gmail.com \
--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