From: David Rientjes <rientjes@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oleg Nesterov <oleg@redhat.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Minchan Kim <minchan.kim@gmail.com>
Subject: Re: [PATCH 2/2][BUGFIX] Revert "oom: deprecate oom_adj tunable"
Date: Wed, 25 Aug 2010 03:27:45 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008250326150.16411@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100825184219.F3F2.A69D9226@jp.fujitsu.com>
On Wed, 25 Aug 2010, KOSAKI Motohiro wrote:
> oom_adj is not only used for kernel knob, but also used for
> application interface.
> Then, adding new knob is no good reason to deprecate it.
>
> Also, after former patch, oom_score_adj can't be used for setting
> OOM_DISABLE. We need "echo -17 > /proc/<pid>/oom_adj" thing.
>
> This reverts commit 51b1bd2ace1595b72956224deda349efa880b693.
Since I nacked the parent patch of this, I implicitly nack this one as
well since oom_score_adj shouldn't be going anywhere. The way to disable
oom killing for a task via the new interface, /proc/pid/oom_score_adj, is
by OOM_SCORE_ADJ_MIN as specified in the documentation.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-08-25 12:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 9:42 [PATCH 1/2][BUGFIX] oom: remove totalpage normalization from oom_badness() KOSAKI Motohiro
2010-08-25 9:42 ` [PATCH 2/2][BUGFIX] Revert "oom: deprecate oom_adj tunable" KOSAKI Motohiro
2010-08-25 10:27 ` David Rientjes [this message]
2010-08-25 10:25 ` [PATCH 1/2][BUGFIX] oom: remove totalpage normalization from oom_badness() David Rientjes
2010-08-26 0:39 ` KAMEZAWA Hiroyuki
2010-08-26 0:52 ` David Rientjes
2010-08-26 1:03 ` KAMEZAWA Hiroyuki
2010-08-26 1:11 ` KAMEZAWA Hiroyuki
2010-08-26 2:50 ` David Rientjes
2010-08-26 3:20 ` KAMEZAWA Hiroyuki
2010-08-26 3:52 ` David Rientjes
2010-08-30 2:58 ` KOSAKI Motohiro
2010-09-01 22:06 ` David Rientjes
2010-09-08 2:44 ` KOSAKI Motohiro
2010-09-08 3:12 ` 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.1008250326150.16411@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=oleg@redhat.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