From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail203.messagelabs.com (mail203.messagelabs.com [216.82.254.243]) by kanga.kvack.org (Postfix) with ESMTP id C47FF8D0039 for ; Wed, 9 Mar 2011 18:36:36 -0500 (EST) Received: from m4.gw.fujitsu.co.jp (unknown [10.0.50.74]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 9C6C33EE0BB for ; Thu, 10 Mar 2011 08:36:32 +0900 (JST) Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id 82A2545DE52 for ; Thu, 10 Mar 2011 08:36:32 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (s4.gw.fujitsu.co.jp [10.0.50.94]) by m4.gw.fujitsu.co.jp (Postfix) with ESMTP id 6AC4E45DE4D for ; Thu, 10 Mar 2011 08:36:32 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 5ABBCE78005 for ; Thu, 10 Mar 2011 08:36:32 +0900 (JST) Received: from ml13.s.css.fujitsu.com (ml13.s.css.fujitsu.com [10.240.81.133]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 0E78CE78002 for ; Thu, 10 Mar 2011 08:36:32 +0900 (JST) Date: Thu, 10 Mar 2011 08:30:11 +0900 From: KAMEZAWA Hiroyuki Subject: Re: [patch] memcg: give current access to memory reserves if it's trying to die Message-Id: <20110310083011.c36247b8.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: References: <20110307171853.c31ec416.akpm@linux-foundation.org> <20110308115108.36b184c5.kamezawa.hiroyu@jp.fujitsu.com> <20110308121332.de003f81.kamezawa.hiroyu@jp.fujitsu.com> <20110308131723.e434cb89.kamezawa.hiroyu@jp.fujitsu.com> <20110308144901.fe34abd0.kamezawa.hiroyu@jp.fujitsu.com> <20110309150452.29883939.kamezawa.hiroyu@jp.fujitsu.com> <20110309161621.f890c148.kamezawa.hiroyu@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: David Rientjes Cc: Andrew Morton , Balbir Singh , Daisuke Nishimura , linux-mm@kvack.org On Wed, 9 Mar 2011 13:27:50 -0800 (PST) David Rientjes wrote: > When a memcg is oom and current has already received a SIGKILL, then give > it access to memory reserves with a higher scheduling priority so that it > may quickly exit and free its memory. > > This is identical to the global oom killer and is done even before > checking for panic_on_oom: a pending SIGKILL here while panic_on_oom is > selected is guaranteed to have come from userspace; the thread only needs > access to memory reserves to exit and thus we don't unnecessarily panic > the machine until the kernel has no last resort to free memory. > > Signed-off-by: David Rientjes Acked-by: KAMEZAWA Hiroyuki Thank you. -- 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: email@kvack.org