From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: OK to set PF_MEMDIE on cleanup tasks?
Date: Tue, 14 Oct 2003 08:17:59 -0700 [thread overview]
Message-ID: <20031014151759.GA2188@us.ibm.com> (raw)
Hello!
We have tasks that actively return memory to the system, which we
would like to exempt from the OOM killer, as killing such tasks under
low-memory conditions would indeed be counterproductive. It looks like
the "official" way to do this is to catch/ignore signal 15, which results
in PF_MEMDIE being set (in the 2.6 kernel), thus preventing the OOM killer
from killing the task again. I don't see where PF_MEMDIE is cleared,
though there are a number of subtle ways one might do this that I would
have missed.
So... Is it considered legit to simply set PF_MEMDIE when creating
the cleanup task? Or is there some reason that one should deal with
signal 15?
All enlightenment much appreciated!
Thanx, Paul
next reply other threads:[~2003-10-14 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 15:17 Paul E. McKenney [this message]
2003-10-15 0:12 ` OK to set PF_MEMDIE on cleanup tasks? Andrew Morton
2003-10-15 1:34 ` Gerrit Huizenga
2003-10-16 17:10 ` Paul E. McKenney
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=20031014151759.GA2188@us.ibm.com \
--to=paulmck@us.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).