From: Dan Kegel <dank@kegel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Protecting processes from the OOM killer
Date: Fri, 28 Feb 2003 08:08:37 -0800 [thread overview]
Message-ID: <3E5F8985.60606@kegel.com> (raw)
In-Reply-To: <1046439618.16599.22.camel@irongate.swansea.linux.org.uk>
Alan Cox wrote:
> On Fri, 2003-02-28 at 01:21, Dan Kegel wrote:
>
>>For a while now, I've been trying to figure out how
>>to make the oom killer not kill important processes.
>
>
> How about by not allowing your system to excessively overcommit.
(I'm using 2.4.18; is
http://www.kernel.org/pub/linux/kernel/people/rml/vm/strict-overcommit/v2.4/vm-strict-overcommit-rml-2.4.18-1.patch
still the approprate patch for that?)
> Everything else is armwaving "works half the time" stuff. By the time
> the OOM kicks in the game is already over.
Even with overcommit disallowed, the OOM killer is going to run
when my users try to run too big a job, so I would still like
the OOM killer to behave "well".
> The rlimit one doesnt deal
> with things like fork explosions where you have lots of processes
> all under 1/4 of the rlimit range who cumulatively overcommit. In
> fact you now pick harder on other tasks...
We do not see fork explosions in our workload, but if we did,
we could abuse the RSS limit for now by setting it to zero except for
the processes we wanted to protect from the OOM killer.
If that works in practice the same idea could be done without the abuse;
the RSS limit is just a handy knob.
- Dan
--
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045
next prev parent reply other threads:[~2003-02-28 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 1:21 Protecting processes from the OOM killer Dan Kegel
2003-02-28 13:40 ` Alan Cox
2003-02-28 14:19 ` Ville Herva
2003-02-28 15:37 ` Alan Cox
2003-02-28 16:08 ` Dan Kegel [this message]
2003-02-28 22:13 ` James Antill
2003-03-03 14:45 ` Jesse Pollard
2003-03-03 16:23 ` Alan Cox
2003-03-03 16:41 ` Dan Kegel
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=3E5F8985.60606@kegel.com \
--to=dank@kegel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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