From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934415AbXFFBlZ (ORCPT ); Tue, 5 Jun 2007 21:41:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933204AbXFFBlQ (ORCPT ); Tue, 5 Jun 2007 21:41:16 -0400 Received: from smtp-out.google.com ([216.239.45.13]:24454 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933190AbXFFBlP (ORCPT ); Tue, 5 Jun 2007 21:41:15 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:date:from:x-x-sender:to:cc:subject:in-reply-to: message-id:references:mime-version:content-type; b=opx/KQldcECiRLwCETBgcQwj7+ECe620Qp8pJNKVfCUOzwFlC2/kG3LoZFvfj/WMT zYKShu9CG0qry4sd8FKcg== Date: Tue, 5 Jun 2007 18:40:34 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Christoph Lameter cc: Paul Jackson , akpm@linux-foundation.org, ak@suse.de, clameter@cthulhu.engr.sgi.com, linux-kernel@vger.kernel.org Subject: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally In-Reply-To: Message-ID: References: <20070605160149.348b5c4a.pj@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 5 Jun 2007, Christoph Lameter wrote: > On Tue, 5 Jun 2007, David Rientjes wrote: > > > Obviously GFP_KERNEL allocations can allocate regardless of our memory > > exclusivity, but the point is that a job in one exclusive cpuset should > > not have the ability to effect the performance (in terms of reclaim and > > swap), memory usage, or survival of jobs in other exclusive cpusets > > because it was out of memory. > > Right but the process is terminating thus only requiring limited resources > to get finished. The process does not have the ability to affect the other > cpusets. I.e. it cannot directly allocate outside of the cpuset. The > system has that capability and the system is handling the termination of > the process and should terminate the process in a clean way if possible. > And those limited resources should be available in the difference between low and no watermarks as defined by each zone in the cpuset's mems_allowed. Regardless, we should not allow allocations outside of the cpuset because we have marked it TIF_MEMDIE and we don't have any explicit guarantee that it is exiting yet and not mlock'ing an excessive amount of memory that exceeds the capacity of all cpuset nodes. David