Re: [PATCH 0/3] mm: use memmap_on_memory semantics for dax/kmem

[David Hildenbrand]

On 21.06.23 21:32, Verma, Vishal L wrote:
> On Fri, 2023-06-16 at 09:44 +0200, David Hildenbrand wrote:
> > On 16.06.23 00:00, Vishal Verma wrote:
> > > The dax/kmem driver can potentially hot-add large amounts of memory
> > > originating from CXL memory expanders, or NVDIMMs, or other 'device
> > > memories'. There is a chance there isn't enough regular system memory
> > > available to fit ythe memmap for this new memory. It's therefore
> > > desirable, if all other conditions are met, for the kmem managed memory
> > > to place its memmap on the newly added memory itself.
> > >
> > > Arrange for this by first allowing for a module parameter override for
> > > the mhp_supports_memmap_on_memory() test using a flag, adjusting the
> > > only other caller of this interface in dirvers/acpi/acpi_memoryhotplug.c,
> > > exporting the symbol so it can be called by kmem.c, and finally changing
> > > the kmem driver to add_memory() in chunks of memory_block_size_bytes().
> >
> > 1) Why is the override a requirement here? Just let the admin configure
> > it then then add conditional support for kmem.
>
> Configure it in the current way using the module parameter to
> memory_hotplug? The whole module param check feels a bit awkward,
> especially since memory_hotplug is builtin, the only way to supply the
> param is on the kernel command line as opposed to a modprobe config.

Yes, and that's nothing special. Runtime toggling is not implemented.

> The goal with extending mhp_supports_memmap_on_memory() to check for
> support with or without consideration for the module param is that it
> makes it a bit more flexible for callers like kmem.

Not convinced yet that the global parameter should be bypassed TBH. And 
if so, this should be a separate patch on top that is completely 
optional for the remainder of the series.


In any case, there has to be some admin control over that, because

1) You usually don't want vmemmap on potentially slow memory
2) Using memmap-on-memory prohibits gigantic pages from forming on that 
memory (when runtime-allocating them).

So "just doing that" without any config knob is problematic.

--
Cheers,

David / dhildenb