From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Peterson Subject: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations Date: Fri, 28 Apr 2006 15:09:03 -0700 References: <200604271308.10080.dsp@llnl.gov> <20060427140921.249a00b0.akpm@osdl.org> <20060427160250.a72cae11.pj@sgi.com> In-Reply-To: <20060427160250.a72cae11.pj@sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604281509.03140.dsp@llnl.gov> Sender: owner-linux-mm@kvack.org Return-Path: To: Paul Jackson , Andrew Morton Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, riel@surriel.com, nickpiggin@yahoo.com.au, ak@suse.de List-ID: On Thursday 27 April 2006 16:02, Paul Jackson wrote: > I'm still a little surprised that this per-mm 'oom_notify' bit > was needed to implement what I thought was a single, global > system wide oom killer serializer. I think the title "mm: serialize OOM kill operations" was probably a poor choice of words. It sounds like all I want to do is make sure tasks enter the OOM killer one-at-a-time. My goal is actually to prevent further OOM kill operations until the OOM kill in progress has caused the victim task to free its address space (i.e. clean out its mm_struct). That way we don't shoot more processes than necessary to resolve the OOM condition. -- 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: email@kvack.org