Re: [RFC PATCH 0/7] Memory hotplug/hotremove at subsection size

David Hildenbrand
2021-05-06T16:28:35Z

On 06.05.21 17:50, Zi Yan wrote:
> On 6 May 2021, at 11:40, David Hildenbrand wrote:
>
>>>>> The last patch increases SECTION_SIZE_BITS to demonstrate the use of memory
>>>>> hotplug/hotremove subsection, but is not intended to be merged as is. It is
>>>>> there in case one wants to try this out and will be removed during the final
>>>>> submission.
>>>>>
>>>>> Feel free to give suggestions and comments. I am looking forward to your
>>>>> feedback.
>>>>
>>>> Please not like this.
>>>
>>> Do you mind sharing more useful feedback instead of just saying a lot of No?
>>
>> I remember reasoning about this already in another thread, no? Either you're ignoring my previous feedback or my mind is messing with me.
>
> I definitely remember all your suggestions:
>
> 1. do not use CMA allocation for 1GB THP.
> 2. section size defines the minimum size in which we can add_memory(), so we cannot increase it.
>
> I am trying an alternative here. I am not using CMA allocation and not increasing the minimum size of add_memory() by decoupling the memory block size from section size, so that add_memory() can add a memory block smaller (as small as 2MB, the subsection size) than section size. In this way, section size can be increased freely. I do not see the strong tie between add_memory() and section size, especially we have subsection bitmap support.

Okay, let me express my thoughts, I could have sworn I explained back
then why I am not a friend of messing with the existing pageblock size:

1. Pageblock size

There are a couple of features that rely on the pageblock size to be
reasonably small to work as expected. One example is virtio-balloon free
page reporting, then there is virtio-mem (still also glued MAX_ORDER)
and we have CMA (still also glued to MAX_ORDER). Most probably there are
more. We track movability/ page isolation per pageblock; it's the
smallest granularity you can effectively isolate pages or mark them as
CMA (MIGRATE_ISOLATE, MIGRATE_CMA). Well, and there are "ordinary" THP /
huge pages most of our applications use and will use, especially on
smallish systems.

Assume you bump up the pageblock order to 1G. Small VMs won't be able to
report any free pages to the hypervisor. You'll take the "fine-grained"
out of virtio-mem. Each CMA area will have to be at least 1G big, which
turns CMA essentially useless on smallish systems (like we have on arm64
with 64k base pages -- pageblock_size is 512MB and I hate it).

Then, imagine systems that have like 4G of main memory. By stopping
grouping at 2M and instead grouping at 1G you can very easily find
yourself in the system where all your 4 pageblocks are unmovable and you
essentially don't optimize for huge pages in that environment any more.

Long story short: we need a different mechanism on top and shall leave
the pageblock size untouched, it's too tightly integrated with page
isolation, ordinary THP, and CMA.

2. Section size

I assume the only reason you want to touch that is because
pageblock_size <= section_size, and I guess that's one of the reasons I
dislike it so much. Messing with the section size really only makes
sense when we want to manage metadata for larger granularity within a
section.

We allocate metadata per section. We mark whole sections
early/online/present/.... Yes, in case of vmemmap, we manage the memmap
in smaller granularity using the sub-section map, some kind of hack to
support some ZONE_DEVICE cases better.

Let's assume we introduce something new "gigapage_order", corresponding
to 1G. We could either decide to squeeze the metadata into sections,
having to increase the section size, or manage that metadata differently.

Managing it differently certainly makes the necessary changes easier.
Instead of adding more hacks into sections, rather manage that metadata
at differently place / in a different way.

See [1] for an alternative. Not necessarily what I would dream off, but
just to showcase that there might be alternative to group pages.

3. Grouping pages > pageblock_order

There are other approaches that would benefit from grouping at >
pageblock_order and having bigger MAX_ORDER. And that doesn't
necessarily mean to form gigantic pages only, we might want to group in
multiple granularity on a single system. Memory hot(un)plug is one
example, but also optimizing memory consumption by powering down DIMM
banks. Also, some architectures support differing huge page sizes
(aarch64) that could be improved without CMA. Why not have more than 2
THP sizes on these systems?

Ideally, we'd have a mechanism that tries grouping on different
granularity, like for every order in pageblock_order ...
max_pageblock_order (e.g., 1 GiB), and not only add one new level of
grouping (or increase the single grouping size).

[1] https://lkml.kernel.org/r/20210414023803.937-1-lipeifeng@oppo.com

--
Thanks,

David / dhildenb