On Mon, Mar 25, 2019 at 3:20 AM Michal Hocko <mhocko@xxxxxxxxxx> wrote: > > On Fri 22-03-19 11:32:11, Dan Williams wrote: > > 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. > > Which is a pageblock unit on x86 with hugetlb enabled. I was just > wondering whether this is really bound to pageblock or the math just > works out to be the same. Ah, ok just coincidental math. > > > 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. > > OK, this is good to know and actually against subsection direction. Seems I forgot to mention timescales. The 64MB granularity is present on current generation platforms, and I expect multiple platform generations (potentially years) until it might change in the future. That does not even take into consideration the configuration flexibility of PCI BAR ranges and the interaction with the peer-to-peer DMA facility which maps 'struct page' for physical ranges that are not memory. There is no pressure for PCI BAR ranges to submit to a 128MB alignment. > > User-defined memory namespaces have this problem, but 2MB is the > > default alignment and is sufficient for most uses. > > What does prevent users to go and use a larger alignment? Given that we are living with 64MB granularity on mainstream platforms for the foreseeable future, the reason users can't rely on a larger alignment to address the issue is that the physical alignment may change from one boot to the next. No, you can't just wish hardware / platform firmware won't do this, because there are not enough platform resources to give every hardware device a guaranteed alignment. The effect is that even if the driver deploys a software alignment mitigation when it first sees the persistent memory range, that alignment can be violated on a subsequent boot leading to data being unavailable. There is no facility to communicate to the administrator what went wrong in this scenario as several events can trigger a physical map layout change. Add / remove of hardware and hardware failure are the most likely causes. An additional pain point for users is that EFI pre-boot environment has little chance to create a namespace that Linux might be able to use. The section size is an arbitrary Linux constraint and we should not encode something Linux specific that might change in the future into OS agnostic software. > > 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 this is exactly the problem. Having different assumptions depending > on whether there is a memblock interface or not is utterly wrong and a > maintainability mess. In this case I disagree with you. The hotplug code already has the want_memblock=false semantic in the implementation. The sub-section hotplug infrastructure is a strict superset of what is there already. Now, if it created parallel infrastructure that would indeed be a maintainability burden, but in this case there are no behavior changes for typical memory hotplug as it just hotplugs full sections at a time like always. The 'section' concept is not going away. > > > 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. > > And why is that a problem? Data loss, inability to cope with some hardware configurations, difficult to interoperate with non-Linux software. > A lack of documentation that this is a requirement? It's not a requirement. It's an arbitrary Linux implementation detail. > Something will not work with a larger alignment? Someting else? [..] > Why do we have to go a mile to tweak the kernel, especially something as > fragile as memory hotplug, just to support sub mem section ranges. This > is somthing that is not clearly explained in the cover letter. Sure you > are talking about hacks at the higher level to deal with this but I do > not see any fundamental reason to actually support that at all. Like it or not, 'struct page' mappings for arbitrary hardware-physical memory ranges is a facility that has grown from the pmem case, to hmm, and peer-to-peer DMA. Unless you want to do the work to eliminate the 'struct page' requirement across the kernel I think it is unreasonable to effectively archive the arch_add_memory() implementation and prevent it from reacting to growing demands. Note that I did try to eliminate 'struct page' before creating devm_memremap_pages(), that effort failed because 'struct page' is just too ingrained into too many kernel code paths. > > I'm also open to exploring lifting the section alignment constraint > > for the 'want_memblock=true', but first things first. > > I disagree. If you want to get rid of the the section requirement then > do it first and build on top. This is a normal kernel development > process. > > > > 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. > > Yes and we are talking about 128MB is sacrifying that unit worth all the > troubles? > > [...] > > > > 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. > > I can feel your frustration. I am not entirely happy about the section > size limitation myself but you have to realize that this is simplicy vs. > feature set compromise. You have to realize that arch_add_memory() is no longer just a front-end for typical memory hotplug. The requirements have changed. Simplicity should be maintained for as long as it can get the job done, and the simplicity is currently failing. > It works reasonably well for many usecases but > falls flat on some others. But you cannot simply build on top of > existing foundations and tweak some code paths to handle one particular > case. This is exactly how the memory hotplug ended in the unfortunate > state it is now. If you want to make the code more reusable then there > is a _lot_ of ground work first before you can add a shiny new feature. This *is* the ground work. It solves the today's hardware page-mapping pain points with a path to go deeper and enable sub-section hotplug for typical memory hotplug, but in the meantime the two cases share common code paths. This is not a tweak on the side, it's a super-set, and typical memory-hotplug is properly fixed up to use just the subset that it needs.
