KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> writes: > This is a page allcoator based on memory migration/hotplug code. > passed some small tests, and maybe easier to read than previous one. Maybe I'm missing context here, but what is the use case for this? If this works well enough the 1GB page code for x86, which currently only supports allocating at boot time due to the MAX_ORDER problem, could be moved over to runtime allocation. This would make GB pages a lot nicer to use. I think it would still need declaring a large moveable area at boot right? (but moveable area is better than prereserved memory) On the other hand I'm not sure the VM is really up to speed in managing such large areas. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- 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/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>