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

[Mike Rapoport]

On Mon, 02 Nov 2026 11:25:22 +0800, Muchun Song <songmuchun@xxxxxxxxxxxxx> 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.
> 
> [...]

Reviewed-by: Mike Rapoport (Microsoft) <rppt@xxxxxxxxxx>

-- 
Sincerely yours,
Mike.