On Fri, 18 Feb 2005, Dave Hansen wrote:
Memory hot-remove isn't really needed with Xen, the balloon driver takes care of that.
You can free up individual pages back to the hypervisor, but you might also want the opportunity to free up some unused mem_map if you shrink the partition by a large amount.
Agreed, though I rather like the fact that the code can be introduced bit by bit, so the memory hot-remove code (probably the most complex part) doesn't need to be maintained out-of-tree for Xen, but can wait until it is upstream.
I can post individual patches if anyone would like to comment on them.
I'm interested. I want to get this stuff working with Xen ;)
You can either pull them from here:
http://www.sr71.net/patches/2.6.11/2.6.11-rc3-mhp1/broken-out/
Thanks, I'll take a stab at porting this functionality to Xen.
-- "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." - Brian W. Kernighan - 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/
