public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Chris Swiedler <chris.swiedler@sevista.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@conectiva.com.br>
Subject: Re: [PATCH] protect processes from OOM killer
Date: Tue, 7 Nov 2000 21:47:52 +0100	[thread overview]
Message-ID: <20001107214752.J7204@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <NDBBIAJKLMMHOGKNMGFNMEADCPAA.chris.swiedler@sevista.com>
In-Reply-To: <NDBBIAJKLMMHOGKNMGFNMEADCPAA.chris.swiedler@sevista.com>; from chris.swiedler@sevista.com on Tue, Nov 07, 2000 at 11:19:37AM -0500

On Tue, Nov 07, 2000 at 11:19:37AM -0500, Chris Swiedler wrote:
> Here's a small patch to allow a user to protect certain PIDs from death-
> by-OOM-killer. It uses the proc entry '/proc/sys/vm/oom_protect'; echo the
> PIDs to be protected:

Please base it upon my OOM-Killer-API patch.

        http://www.tu-chemnitz.de/~ioe/oom_kill_api.patch

This will reduce your patch to an simple module (but you have to
manage refcounting yourself!) and give the user a choice, which
one to use.

If someone provides an OOM-Handler himself, please use my API to
allow better testing and comparing.

PS: Of course it applies cleanly against test10 as well ;-)

Thanks and Regards

Ingo Oeser
-- 
To the systems programmer, users and applications
serve only to provide a test load.
<esc>:x
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-07 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-07 16:19 [PATCH] protect processes from OOM killer Chris Swiedler
2000-11-07 20:47 ` Ingo Oeser [this message]
2000-11-07 21:44 ` Frank van Maarseveen
2000-12-02  2:20 ` Path: for oom_kill.c hugang
2000-12-04 16:57   ` Rik van Riel
2000-12-04 17:52     ` Jeff Epler

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=20001107214752.J7204@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=chris.swiedler@sevista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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