Date: Sun, 5 Feb 2006 23:08:16 -0800
From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: dgc@sgi.com, steiner@sgi.com, Simon.Derr@bull.net, ak@suse.de,
       linux-kernel@vger.kernel.org, clameter@sgi.com
Subject: Re: [PATCH 1/5] cpuset memory spread basic implementation
Message-Id: <20060205230816.4ae6b6e2.akpm@osdl.org>
In-Reply-To: <20060205225629.5d887661.pj@sgi.com>
References: <20060204071910.10021.8437.sendpatchset@jackhammer.engr.sgi.com>
	<20060205203711.2c855971.akpm@osdl.org>
	<20060205225629.5d887661.pj@sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1304
Lines: 35

Paul Jackson <pj@sgi.com> wrote:
>
> Andrew wrote:
> > IOW: this patch seems to be a highly specific bandaid which is repairing an
> > ill-advised problem of our own making, does it not?
> 
> 
> I am mystified.  I am unable to imagine how you see this memory
> spreading patchset as a response to some damage caused by previous
> work.

Node-local allocation.

> 
> So, the user must tell the kernel it needs this.
>

Well I agree.  And I think that the only way we'll get peak performance for
an acceptaly broad range of applications is to provide many fine-grained
controls and the appropriate documentation and instrumentation to help
developers and administrators use those controls.

We're all on the same page here.  I'm questioning whether slab and
pagecache should be inextricably lumped together though.

Is it possible to integrate the slab and pagecache allocation policies more
cleanly into a process's mempolicy?  Right now, MPOL_* are disjoint.

(Why is the spreading policy part of cpusets at all?  Shouldn't it be part
of the mempolicy layer?)
-
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/