Re: [PATCH v2 1/3] mm/memory_hotplug: Export symbol mhp_supports_memmap_on_memory()

Vishal Verma writes: > In preparation for dax drivers, which can be built as modules, > to use this interface, export it with EXPORT_SYMBOL_GPL(). Add a #else > case for the symbol for builds without CONFIG_MEMORY_HOTPLUG. > > Cc: Andrew Morton > Cc: David Hildenbrand > Cc: Oscar Salvador > Cc

Re: [PATCH v2 2/3] mm/memory_hotplug: split memmap_on_memory requests across memblocks

Vishal Verma writes: > The MHP_MEMMAP_ON_MEMORY flag for hotplugged memory is currently > restricted to 'memblock_size' chunks of memory being added. Adding a > larger span of memory precludes memmap_on_memory semantics. > > For users of hotplug such as kmem, large amounts of memory might get > a

Re: [PATCH v2 2/3] mm/memory_hotplug: split memmap_on_memory requests across memblocks

"Aneesh Kumar K.V" writes: > Vishal Verma writes: > >> The MHP_MEMMAP_ON_MEMORY flag for hotplugged memory is currently >> restricted to 'memblock_size' chunks of memory being added. Adding a >> larger span of memory precludes memmap_on_memory semantics. >> >> For users of hotplug such as kmem,

Re: [PATCH v2 2/3] mm/memory_hotplug: split memmap_on_memory requests across memblocks

Vishal Verma writes: > The MHP_MEMMAP_ON_MEMORY flag for hotplugged memory is currently > restricted to 'memblock_size' chunks of memory being added. Adding a > larger span of memory precludes memmap_on_memory semantics. > > For users of hotplug such as kmem, large amounts of memory might get > a