From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail137.messagelabs.com (mail137.messagelabs.com [216.82.249.19]) by kanga.kvack.org (Postfix) with SMTP id EAE388D0017 for ; Sun, 14 Nov 2010 19:22:31 -0500 (EST) Received: from m2.gw.fujitsu.co.jp ([10.0.50.72]) by fgwmail7.fujitsu.co.jp (Fujitsu Gateway) with ESMTP id oAF0MT0m030175 for (envelope-from kosaki.motohiro@jp.fujitsu.com); Mon, 15 Nov 2010 09:22:29 +0900 Received: from smail (m2 [127.0.0.1]) by outgoing.m2.gw.fujitsu.co.jp (Postfix) with ESMTP id E4BCD45DE55 for ; Mon, 15 Nov 2010 09:22:28 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (s2.gw.fujitsu.co.jp [10.0.50.92]) by m2.gw.fujitsu.co.jp (Postfix) with ESMTP id B9B7E45DE4F for ; Mon, 15 Nov 2010 09:22:28 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id 984C31DB8040 for ; Mon, 15 Nov 2010 09:22:28 +0900 (JST) Received: from m105.s.css.fujitsu.com (m105.s.css.fujitsu.com [10.249.87.105]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id 50D511DB803B for ; Mon, 15 Nov 2010 09:22:28 +0900 (JST) From: KOSAKI Motohiro Subject: Re: [patch] oom: document obsolete oom_adj tunable In-Reply-To: References: Message-Id: <20101115091908.BEEB.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Mon, 15 Nov 2010 09:22:27 +0900 (JST) Sender: owner-linux-mm@kvack.org To: David Rientjes Cc: kosaki.motohiro@jp.fujitsu.com, Alan Cox , Andrew Morton , Linus Torvalds , linux-kernel@vger.kernel.org, linux-mm@kvack.org List-ID: > /proc/pid/oom_adj was deprecated in August 2010 with the introduction of > the new oom killer heuristic. > > This patch copies the Documentation/feature-removal-schedule.txt entry > for this tunable to the Documentation/ABI/obsolete directory so nobody > misses it. > > Reported-by: Alan Cox > Signed-off-by: David Rientjes NAK. You seems to think shouting claim makes some effect. but It's incorrect. Your childish shout doesn't solve any real world issue. Only code fix does. > --- > Documentation/ABI/obsolete/proc-pid-oom_adj | 22 ++++++++++++++++++++++ > 1 files changed, 22 insertions(+), 0 deletions(-) > create mode 100644 Documentation/ABI/obsolete/proc-pid-oom_adj > > diff --git a/Documentation/ABI/obsolete/proc-pid-oom_adj b/Documentation/ABI/obsolete/proc-pid-oom_adj > new file mode 100644 > --- /dev/null > +++ b/Documentation/ABI/obsolete/proc-pid-oom_adj > @@ -0,0 +1,22 @@ > +What: /proc//oom_adj > +When: August 2012 > +Why: /proc//oom_adj allows userspace to influence the oom killer's > + badness heuristic used to determine which task to kill when the kernel > + is out of memory. > + > + The badness heuristic has since been rewritten since the introduction of > + this tunable such that its meaning is deprecated. The value was > + implemented as a bitshift on a score generated by the badness() > + function that did not have any precise units of measure. With the > + rewrite, the score is given as a proportion of available memory to the > + task allocating pages, so using a bitshift which grows the score > + exponentially is, thus, impossible to tune with fine granularity. > + > + A much more powerful interface, /proc//oom_score_adj, was > + introduced with the oom killer rewrite that allows users to increase or > + decrease the badness() score linearly. This interface will replace > + /proc//oom_adj. Incorrect. oom_adj and oom_score_adj have different concept and different abstraction. One can't replace another. > + > + A warning will be emitted to the kernel log if an application uses this > + deprecated interface. After it is printed once, future warnings will be > + suppressed until the kernel is rebooted. -- 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 policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: email@kvack.org