From: David Rientjes <rientjes@google.com>
To: Dave Chinner <david@fromorbit.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [3.2-rc3] OOM killer doesn't kill the obvious memory hog
Date: Thu, 1 Dec 2011 14:35:31 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.00.1112011432110.27778@chino.kir.corp.google.com> (raw)
In-Reply-To: <20111201124634.GY7046@dastard>
On Thu, 1 Dec 2011, Dave Chinner wrote:
> > /*
> > * /proc/<pid>/oom_score_adj set to OOM_SCORE_ADJ_MIN disables oom killing for
> > * pid.
> > */
> > #define OOM_SCORE_ADJ_MIN (-1000)
> >
> >
> > IIUC, this task cannot be killed by oom-killer because of oom_score_adj settings.
>
> It's not me or the test suite that setting this, so it's something
> the kernel must be doing automagically.
>
The kernel does not set oom_score_adj to ever disable oom killing for a
thread. The only time the kernel touches oom_score_adj is when setting it
to "1000" in ksm and swap to actually prefer a memory allocator for oom
killing.
It's also possible to change this value via the deprecated
/proc/pid/oom_adj interface until it is removed next year. Check your
dmesg for warnings about using the deprecated oom_adj interface or change
the printk_once() in oom_adjust_write() to a normal printk() to catch it.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-12-01 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 9:36 Dave Chinner
2011-12-01 9:50 ` KAMEZAWA Hiroyuki
2011-12-01 12:46 ` Dave Chinner
2011-12-01 22:35 ` David Rientjes [this message]
2011-12-02 1:59 ` Dave Chinner
2011-12-02 3:31 ` Dave Chinner
2011-12-02 5:44 ` KAMEZAWA Hiroyuki
2011-12-04 22:04 ` Dave Chinner
2011-12-06 20:31 ` 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=alpine.DEB.2.00.1112011432110.27778@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=david@fromorbit.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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