On Mon, Aug 11, 2014 at 09:31:22PM +0800, Xishi Qiu wrote: > Let memblock skip the hotpluggable memory regions in __next_mem_range(), > it is used to to prevent memblock from allocating hotpluggable memory > for the kernel at early time. The code is the same as __next_mem_range_rev(). > > Clear hotpluggable flag before releasing free pages to the buddy allocator.
Please try to explain "why" in addition to "what". Why do we need to clear hotpluggable flag in free_low_memory_core_early() in addition to numa_clear_node_hotplug() in x86 numa.c? Does this make x86 code redundant? If not, why? -- tejun -- 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/
