Date: Tue, 1 Nov 2005 09:19:22 -0800 (PST)
From: Christoph Lameter <clameter@engr.sgi.com>
To: Andrew Morton <akpm@osdl.org>
cc: torvalds@osdl.org, kravetz@us.ibm.com, raybry@mpdtxmail.amd.com,
       linux-kernel@vger.kernel.org, lee.schermerhorn@hp.com,
       haveblue@us.ibm.com, magnus.damm@gmail.com, pj@sgi.com,
       marcelo.tosatti@cyclades.com, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH 0/5] Swap Migration V5: Overview
In-Reply-To: <20051031192506.100d03fa.akpm@osdl.org>
Message-ID: <Pine.LNX.4.62.0511010916400.16157@schroedinger.engr.sgi.com>
References: <20051101031239.12488.76816.sendpatchset@schroedinger.engr.sgi.com>
 <20051031192506.100d03fa.akpm@osdl.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1088
Lines: 25

On Mon, 31 Oct 2005, Andrew Morton wrote:

> So I'll queue this up for -mm, but I think we need to see an entire
> hot-remove implementation based on this, and have all the interested
> parties signed up to it before we can start moving the infrastructure into
> mainline.

There are multiple components involved here. This includes user space, 
cpusets and kernel support for various forms of migrating pages.

> Do you think the features which these patches add should be Kconfigurable?

The policy layer stuff is already Kconfigurable via CONFIG_NUMA. 

I think the lower layer in vmscan.c could be always included since its 
currently small and its just a variation on swap. However, if we add the 
rest of the features contained in the hot plug then the code size becomes 
significant and we may want to have a config variable for that.


-
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/