On Thu, 18 Nov 2010, Paul Mundt wrote: > This is all stuff that the memblock API can deal with, I'm not sure why > there seems to be an insistence on wedging all manner of unrelated bits > in to e820. Many platforms using memblock today already offline large > amounts of contiguous physical memory for use in drivers, if you were to > follow this scheme and simply layer a node creation shim on top of that > you would end up with something that is almost entirely generic. > I don't see why this patchset needs to use the memblock API at all, it should be built entirely on the generic mem-hotplug API. The only extension needed is the remapping of removed memory to a new node id (done on x86 with update_nodes_add()) prior to add_memory() for each arch that supports onlining new nodes. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>