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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
