Re: [PATCH 09/12] mm: hugetlb_vmemmap: make vmemmap optimization folio-oriented

[Lance Yang]

On Tue, Oct 20, 2026 at 07:58:21PM +0800, Muchun Song wrote:
>Vmemmap optimization operates on one folio at a time, but the current
>interface exposes a raw address range and requires the HugeTLB caller to
>prepare part of the operation.  This splits the common mechanism across
>layers and obscures its natural unit of work.
>
>Make the folio the unit of vmemmap optimization and move the common
>mechanics behind a folio-oriented interface.  This keeps HugeTLB-specific
>eligibility and state in the caller while making the remapping code
>applicable to any eligible folio.
>
>No functional change intended.
>
>Signed-off-by: Muchun Song <songmuchun@xxxxxxxxxxxxx>
>---

Cool, I like having the helper work out the range itself. One less thing
for callers to get wrong :)

Nothing jumped out at me, so:

Reviewed-by: Lance Yang <lance.yang@xxxxxxxxx>