On 6/13/22 07:35, Muchun Song wrote: > It it inconvenient to mention the feature of optimizing vmemmap pages associated > with HugeTLB pages when communicating with others since there is no specific or > abbreviated name for it when it is first introduced. Let us give it a name HVO > (HugeTLB Vmemmap Optimization) from now. > Just thought I would throw this suggestion, even though I am probably too late. I find the term "vmemmap deduplication" more self-explanatory (at least for me) to refer to your technique ,and similarly s/optimize/dedup. Or vmemmap tail page deduplication (too verbose maybe) because really that's what this optimization is all about. OTOH it would slightly deviate from what maybe established now in hugetlb code.
