From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: npiggin@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [patch] oom: prevent livelock when oom_kill_allocating_task is set
Date: Thu, 30 Apr 2009 15:49:20 -0700 [thread overview]
Message-ID: <20090430154920.64c9c866.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0904301538270.12627@chino.kir.corp.google.com>
On Thu, 30 Apr 2009 15:38:53 -0700 (PDT)
David Rientjes <rientjes@google.com> wrote:
> When /proc/sys/vm/oom_kill_allocating_task is set for large systems that
> want to avoid the lengthy tasklist scan, it's possible to livelock if
> current is ineligible for oom kill. This normally happens when it is set
> to OOM_DISABLE, but is also possible if any threads are sharing the same
> ->mm with a different tgid.
OK... And how does the patch address this problem?
<reads the code>
Seems that if we were unable to kill `current', we'll ignore the
oom_kill_allocating_task setting and will fall back the slow tasklist
scan?
next prev parent reply other threads:[~2009-04-30 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 22:38 David Rientjes
2009-04-30 22:49 ` Andrew Morton [this message]
2009-04-30 22:58 ` David Rientjes
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=20090430154920.64c9c866.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=rientjes@google.com \
/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
all inboxes | Powered by JetHome®