> because we have found and mapped all the memory in the system at early time. > > But it is not easy to solve. > 1. We still have to know how much memory and cpus the boot PXM has. > How could we know that ? SRAT again ? yes, need to parse numa info early, and only use RAM for PXM(X) at first. > 2. The boot PXM could have little memory, and we meet the kexec and kdump > problem again. could extend to have more PXM at first, like boot pxm mask. > 3. I'm not quite sure is there any important benefit that the kernel > initializes all > the memory at beginning ? > > And also, the memory hotplug schedule is very tough for us. We really want the > movablenode functionality could be available soon. And this idea could > be a long way to go. So I also think this would be the next step. uh? I already tried best to help. Even spent time to produce patchset to separate acpi_override find/copy, and numa_info parse early and put page tables on local nodes. Let me know what else I could help. Thanks Yinghai -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>