From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 13 Sep 2007 11:32:53 -0700 (PDT) From: David Rientjes Subject: Re: [PATCH 04 of 24] serialize oom killer In-Reply-To: Message-ID: References: <871b7a4fd566de081120.1187786931@v2.random> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: pj@sgi.com, Andrea Arcangeli , linux-mm@kvack.org List-ID: On Wed, 12 Sep 2007, Christoph Lameter wrote: > We are already serializing the cpuset lock. cpuset_lock takes a per cpuset > mutex! So OOM killing is already serialized per cpuset as it should be. > The problem is that cpuset_lock() is a mutex and doesn't exit the OOM killer immediately if it can't be locked. This is a problem that we've encountered before where multiple tasks enter the OOM killer and sleep waiting for the lock. Then one instance of the OOM killer kills current and the cpuset is no longer OOM, but the other threads waiting on the mutex will still kill tasks unnecessarily after taking cpuset_lock(). David -- 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