We need to add some functionality for use by Dynamic NUMA to pieces of mm/, so provide the Kconfig prior to adding actual Dynamic NUMA functionality. For details on Dynamic NUMA, see te later patch (which adds baseline functionality): "mm: add memlayout & dnuma to track pfn->nid & transplant pages between nodes" --- mm/Kconfig | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/mm/Kconfig b/mm/Kconfig index e742d06..bfbe300 100644 --- a/mm/Kconfig +++ b/mm/Kconfig @@ -169,6 +169,30 @@ config MOVABLE_NODE config HAVE_BOOTMEM_INFO_NODE def_bool n +config DYNAMIC_NUMA + bool "Dynamic Numa: Allow NUMA layout to change after boot time" + depends on NUMA + depends on !DISCONTIGMEM + depends on MEMORY_HOTPLUG # locking + mem_online_node(). + help + Dynamic Numa (DNUMA) allows the movement of pages between NUMA nodes at + run time. + + Typically, this is used on systems running under a hypervisor which + may move the running VM based on the hypervisors needs. On such a + system, this config option enables Linux to update it's knowledge of + the memory layout. + + If the feature is not used but is enabled, there is a very small + amount of overhead (an additional pageflag check) is added to all page frees. + + This is only useful if you enable some of the additional options to + allow modifications of the numa memory layout (either through hypervisor events + or a userspace interface). + + Choose Y if you have are running linux under a hypervisor that uses + this feature, otherwise choose N if unsure. + # eventually, we can have this option just 'select SPARSEMEM' config MEMORY_HOTPLUG bool "Allow for memory hot-add" -- 1.8.2.2 -- 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>