Date: Mon, 6 Feb 2006 06:42:53 -0800
From: Paul Jackson <pj@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: ak@suse.de, akpm@osdl.org, dgc@sgi.com, steiner@sgi.com,
       Simon.Derr@bull.net, linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: [PATCH 1/5] cpuset memory spread basic implementation
Message-Id: <20060206064253.d5328e2b.pj@sgi.com>
In-Reply-To: <20060206102337.GA3359@elte.hu>
References: <20060204071910.10021.8437.sendpatchset@jackhammer.engr.sgi.com>
	<200602061109.45788.ak@suse.de>
	<20060206101156.GA1761@elte.hu>
	<200602061116.44040.ak@suse.de>
	<20060206102337.GA3359@elte.hu>
Organization: SGI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 827
Lines: 19

Ingo wrote:
> the case Paul's patch is addressing: workloads which are 
> known to be global (and hence spreading out is the best-performing 
> allocation).

Just to be clear, note that even in my case, we require the node-local
policy for some allocations (into the users portion of the address
space) at the same time we require the spread policy (not
sure I like 'global' here) for other allocations (file stuff).

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401
-
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/