>>>> Reason I am asking is because I wonder how that would interact with the >>>> memory block device infrastructure and hotplugging of system ram - >>>> add_memory()/add_memory_resource(). I *assume* you are not changing the >>>> add_memory() interface, so that one still only works with whole sections >>>> (or well, memory_block_size_bytes()) - check_hotplug_memory_range(). >>> >>> Like you found below, the implementation enforces that add_memory_*() >>> interfaces maintain section alignment for @start and @size. >>> >>>> In general, mix and matching system RAM and persistent memory per >>>> section, I am not a friend of that. >>> >>> You have no choice. The platform may decide to map PMEM and System RAM >>> in the same section because the Linux section is too large compared to >>> typical memory controller mapping granularity capability. >> >> I might be very wrong here, but do we actually care about something like >> 64MB getting lost in the cracks? I mean if it simplifies core MM, let go >> of the couple of MB of system ram and handle the PMEM part only. Treat >> the system ram parts like memory holes we already have in ordinary >> sections (well, there we simply set the relevant struct pages to >> PG_reserved). Of course, if we have hundreds of unaligned devices and >> stuff will start to add up ... but I assume this is not the case? > > That's precisely what we do today and it has become untenable as the > collision scenarios pile up. This thread [1] is worth a read if you > care about some of the gory details why I'm back to pushing for > sub-section support, but most if it has already been summarized in the > current discussion on this thread. Thanks, exactly what I am interested in, will have a look! >>> >>> I don't see a strong reason why not, as long as it does not regress >>> existing use cases. It might need to be an opt-in for new tooling that >>> is aware of finer granularity hotplug. That said, I have no pressing >>> need to go there and just care about the arch_add_memory() capability >>> for now. >> >> Especially onlining/offlining of memory might end up very ugly. And that >> goes hand in hand with memory block devices. They are either online or >> offline, not something in between. (I went that path and Michal >> correctly told me why it is not a good idea) > > Thread reference? Sure: https://marc.info/?l=linux-mm&m=152362539714432&w=2 Onlining/offlining subsections was what I tried. (adding/removing whole sections). But with the memory block device model (online/offline memory blocks), this really was in some sense dirty, although it worked. > >> I was recently trying to teach memory block devices who their owner is / >> of which type they are. Right now I am looking into the option of using >> drivers. Memory block devices that could belong to different drivers at >> a time are well ... totally broken. > > Sub-section support is aimed at a similar case where different > portions of an 128MB span need to handed out to devices / drivers with > independent lifetimes. Right, but we are stuck here with memory block devices having certain bigger granularity. We already went from 128MB to 2048MB because "there were too many". Modeling this on 2MB level (e.g. subsections), no way. And as I said, multiple users for one memory block device, very ugly. What would be interesting is having memory block devices of variable size. (64MB, 1024GB, 6GB ..), maybe even representing the unit in which e.g. add_memory() was performed. But it would also have downsides when it comes to changing the zone of memory blocks. Memory would be onlined/offlined in way bigger chunks. E.g. one DIMM = one memory block device. > >> I assume it would still be a special >> case, though, but conceptually speaking about the interface it would be >> allowed. >> >> Memory block devices (and therefore 1..X sections) should have one owner >> only. Anything else just does not fit. > > Yes, but I would say the problem there is that the > memory-block-devices interface design is showing its age and is being > pressured with how systems want to deploy and use memory today. Maybe, I guess the main "issue" started to pop up when different things (RAM vs. PMEM) were started to be mapped into memory side by side. But it is ABI, and basic kdump would completely break if removed. And of course memory unplug and much more. It is a crucial part of how system ram is handled today and might not at all be easy to replace. -- Thanks, David / dhildenb
