Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750785AbZLOFAq (ORCPT ); Tue, 15 Dec 2009 00:00:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750739AbZLOFAp (ORCPT ); Tue, 15 Dec 2009 00:00:45 -0500 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:35064 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750729AbZLOFAo (ORCPT ); Tue, 15 Dec 2009 00:00:44 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Tue, 15 Dec 2009 13:57:38 +0900 From: KAMEZAWA Hiroyuki To: KAMEZAWA Hiroyuki Cc: David Rientjes , Andrew Morton , Daisuke Nishimura , KOSAKI Motohiro , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Christoph Lameter Subject: Re: [BUGFIX][PATCH] oom-kill: fix NUMA consraint check with nodemask v4.2 Message-Id: <20091215135738.93e49d56.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20091215133546.6872fc4f.kamezawa.hiroyu@jp.fujitsu.com> References: <20091110162121.361B.A69D9226@jp.fujitsu.com> <20091110171704.3800f081.kamezawa.hiroyu@jp.fujitsu.com> <20091111112404.0026e601.kamezawa.hiroyu@jp.fujitsu.com> <20091111134514.4edd3011.kamezawa.hiroyu@jp.fujitsu.com> <20091111142811.eb16f062.kamezawa.hiroyu@jp.fujitsu.com> <20091111152004.3d585cee.kamezawa.hiroyu@jp.fujitsu.com> <20091111153414.3c263842.kamezawa.hiroyu@jp.fujitsu.com> <20091118095824.076c211f.kamezawa.hiroyu@jp.fujitsu.com> <20091214171632.0b34d833.akpm@linux-foundation.org> <20091215103202.eacfd64e.kamezawa.hiroyu@jp.fujitsu.com> <20091215133546.6872fc4f.kamezawa.hiroyu@jp.fujitsu.com> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 2.5.0 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1318 Lines: 40 On Tue, 15 Dec 2009 13:35:46 +0900 KAMEZAWA Hiroyuki wrote: > On Mon, 14 Dec 2009 20:30:37 -0800 (PST) > David Rientjes wrote: > > > 2 ideas which I can think of now are.. > > > 1) add sysctl_oom_calc_on_committed_memory > > > If this is set, use vm-size instead of rss. > > > > > > > I would agree only if the oom killer used total_vm as a the default, it is > > long-standing and allows for the aforementioned capability that you lose > > with rss. I have no problem with the added sysctl to use rss as the > > baseline when enabled. > > > I'll prepare a patch for adds > > sysctl_oom_kill_based_on_rss (default=0) > Hmm.. But for usual desktop users, using rss as default,as memory-eater-should-die. sounds reasoable to me. Hmm...maybe some automatic detection logic is required. As my 1st version shows, CONSTRAINT_CPUSET -> use vm_size CONSTRAINT_LOWMEM -> use lowmem_rss CONSTRAINT_NONE -> use rss seems like a landing point for all stake holders. No ? Thanks, -Kame -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/