Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752798Ab0BZFyX (ORCPT ); Fri, 26 Feb 2010 00:54:23 -0500 Received: from TYO202.gate.nec.co.jp ([202.32.8.206]:59448 "EHLO tyo202.gate.nec.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752597Ab0BZFyV (ORCPT ); Fri, 26 Feb 2010 00:54:21 -0500 Date: Fri, 26 Feb 2010 14:47:52 +0900 From: Daisuke Nishimura To: KAMEZAWA Hiroyuki Cc: "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , "balbir@linux.vnet.ibm.com" , rientjes@google.com, nishimura@mxp.nes.nec.co.jp Subject: Re: [RFC][PATCH 1/2] memcg: oom kill handling improvement Message-Id: <20100226144752.19734ff0.nishimura@mxp.nes.nec.co.jp> In-Reply-To: <20100226142339.7a67f1a8.kamezawa.hiroyu@jp.fujitsu.com> References: <20100224165921.cb091a4f.kamezawa.hiroyu@jp.fujitsu.com> <20100226131552.07475f9c.nishimura@mxp.nes.nec.co.jp> <20100226142339.7a67f1a8.kamezawa.hiroyu@jp.fujitsu.com> Organization: NEC Soft, Ltd. X-Mailer: Sylpheed 2.6.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: 1510 Lines: 34 On Fri, 26 Feb 2010 14:23:39 +0900, KAMEZAWA Hiroyuki wrote: > On Fri, 26 Feb 2010 13:15:52 +0900 > Daisuke Nishimura wrote: > > > On Wed, 24 Feb 2010 16:59:21 +0900, KAMEZAWA Hiroyuki wrote: > > > These are dump of patches just for showing concept, what I want to do. > > > But not tested. please see if you have free time. (you can ignore ;) > > > > > > Anyway, this will HUNK to the latest mmotm, Kirill's work is merged. > > > > > > This is not related to David's work. I don't hesitate to rebase mine > > > to the mmotm if his one is merged, it's easy. > > > But I'm not sure his one goes to mm soon. > > > > > > 1st patch is for better handling oom-kill under memcg. > > It's bigger than I expected, but it basically looks good to me. > > > > BTW, do you think we need quick fix ? I can't think of a very easy/small fix > which is very correct... To be honest, yes. IMHO, casing global oom because of memcg's oom is a very bad behavior in the sence of resource isolation. But I agree it's hard to fix in simple way, so leave it as it is for now.. hmm.. I must admit that I've not done enough oom test under very high pressure. Thanks, Daisuke Nishimura. -- 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/