On Fri, Mar 22, 2019 at 11:06 AM Michal Hocko <mhocko@xxxxxxxxxx> wrote: > > On Fri 22-03-19 09:57:54, Dan Williams wrote: > > Changes since v4 [1]: > > - Given v4 was from March of 2017 the bulk of the changes result from > > rebasing the patch set from a v4.11-rc2 baseline to v5.1-rc1. > > > > - A unit test is added to ndctl to exercise the creation and dax > > mounting of multiple independent namespaces in a single 128M section. > > > > [1]: https://lwn.net/Articles/717383/ > > > > --- > > > > Quote patch7: > > > > "The libnvdimm sub-system has suffered a series of hacks and broken > > workarounds for the memory-hotplug implementation's awkward > > section-aligned (128MB) granularity. For example the following backtrace > > is emitted when attempting arch_add_memory() with physical address > > ranges that intersect 'System RAM' (RAM) with 'Persistent Memory' (PMEM) > > within a given section: > > > > WARNING: CPU: 0 PID: 558 at kernel/memremap.c:300 devm_memremap_pages+0x3b5/0x4c0 > > devm_memremap_pages attempted on mixed region [mem 0x200000000-0x2fbffffff flags 0x200] > > [..] > > Call Trace: > > dump_stack+0x86/0xc3 > > __warn+0xcb/0xf0 > > warn_slowpath_fmt+0x5f/0x80 > > devm_memremap_pages+0x3b5/0x4c0 > > __wrap_devm_memremap_pages+0x58/0x70 [nfit_test_iomap] > > pmem_attach_disk+0x19a/0x440 [nd_pmem] > > > > Recently it was discovered that the problem goes beyond RAM vs PMEM > > collisions as some platform produce PMEM vs PMEM collisions within a > > given section. The libnvdimm workaround for that case revealed that the > > libnvdimm section-alignment-padding implementation has been broken for a > > long while. A fix for that long-standing breakage introduces as many > > problems as it solves as it would require a backward-incompatible change > > to the namespace metadata interpretation. Instead of that dubious route > > [2], address the root problem in the memory-hotplug implementation." > > > > The approach is taken is to observe that each section already maintains > > an array of 'unsigned long' values to hold the pageblock_flags. A single > > additional 'unsigned long' is added to house a 'sub-section active' > > bitmask. Each bit tracks the mapped state of one sub-section's worth of > > capacity which is SECTION_SIZE / BITS_PER_LONG, or 2MB on x86-64. > > So the hotplugable unit is pageblock now, right? No, with this patchset the hotplug unit is 2MB. > Why is this sufficient? 2MB is sufficient because it allows mapping a namespace at PMD granularity and there is no practical need to go smaller. > What prevents new and creative HW to come up with alignements that do not fit there? There is a resource in hardware memory controllers called address-decode-registers that control the mapping granularity. The minimum granularity today is 64MB and the pressure as memory sizes increases is to make that granularity larger, not smaller. So the hardware pressure is going in the opposite direction of your concern, at least for persistent memory. User-defined memory namespaces have this problem, but 2MB is the default alignment and is sufficient for most uses. PCI Address BARs that are also mapped with devm_memremap_pages are aligned to their size and there is no expectation to support smaller than 2MB. All that said, to support a smaller sub-section granularity, just add more bits to the section-active bitmask. > Do not get me wrong but the section > as a unit is deeply carved into the memory hotplug and removing all those > assumptions is a major undertaking Right, as stated in the cover letter, this does not remove all those assumptions, it only removes the ones that impact devm_memremap_pages(). Specifying that sub-section is only supported in the 'want_memblock=false' case to arch_add_memory(). > and I would like to know that you are > not just shifting the problem to a smaller unit and a new/creative HW > will force us to go even more complicated. HW will not do this to us. It's software that has the problem. Namespace creation is unnecessarily constrained to 128MB alignment. I'm also open to exploring lifting the section alignment constraint for the 'want_memblock=true', but first things first. > What is the fundamental reason that pmem sections cannot be assigned > to a section aligned memory range? The physical address space is > quite large to impose 128MB sections IMHO. I thought this is merely a > configuration issue. 1) it's not just hardware that imposes this, software wants to be able to avoid the constraint 2) the flexibility of the memory controller initialization code is constrained by address-decode-registers. So while it is simple to say "just configure it to be aligned" it's not that easy in practice without throwing away usable memory capacity. > How often this really happens and how often it is unavoidable. Again, software can cause this problem at will. Multiple shipping systems expose this alignment problem in physical address space, for example: https://github.com/pmem/ndctl/issues/76 > > The implication of allowing sections to be piecemeal mapped/unmapped is > > that the valid_section() helper is no longer authoritative to determine > > if a section is fully mapped. Instead pfn_valid() is updated to consult > > the section-active bitmask. Given that typical memory hotplug still has > > deep "section" dependencies the sub-section capability is limited to > > 'want_memblock=false' invocations of arch_add_memory(), effectively only > > devm_memremap_pages() users for now. > > Does this mean that pfn_valid is more expensive now? How much? Negligible, the information to determine whether the sub-section is valid for a given pfn is in the same cacheline as the section-valid flag. > Also what about the section life time? Section is live as long as any sub-section is active. > Who is removing section now? Last arch_remove_memory() that removes the last sub-section clears out the remaining sub-section active bits. > I will probably have much more question, but it's friday and I am mostly > offline already. I would just like to hear much more about the new > design and resulting assumptions. Happy to accommodate this discussion. The section alignment has been an absolute horror to contend with. So I have years worth of pain to share for as deep as you want to go on probing why this is needed.
