Re: [PATCH v1 05/11] mm/sparse-vmemmap: add a pgmap argument to section activation
Dan Williams <[email protected]> Wed, 5 May 2021 15:34:54 -0700
| Newsgroups | org.01.lists.linux-nvdimm,org.kvack.linux-mm |
|---|---|
| Message-ID | <CAPcyv4iOh5wS04F=hftcwN1e3DJTg-qUhw8KHR=+wncqJ2KZsg@mail.gmail.com> |
On Thu, Mar 25, 2021 at 4:10 PM Joao Martins <[email protected]> wrote: > > @altmap is stored in a dev_pagemap, but it will be repurposed for > hotplug memory for storing the memmap in the hotplugged memory[*] and > reusing the altmap infrastructure to that end. This is to say that > altmap can't be replaced with a @pgmap as it is going to cover more than > dev_pagemap backend altmaps. I was going to say, just pass the pgmap and lookup the altmap from pgmap, but Oscar added a use case for altmap independent of pgmap. So you might refresh this commit message to clarify why passing pgmap by itself is not sufficient. Other than that, looks good. _______________________________________________ Linux-nvdimm mailing list -- [email protected] To unsubscribe send an email to [email protected]