Re: [PATCH v2 3/7] mm/page_ext: always use vmalloc for section page extensions

From: Mike Rapoport

Date: Wed Nov 18 2026 - 08:44:11 EST


On Tue, Nov 17, 2026 at 08:06:23PM +0800, Muchun Song wrote:
> SPARSEMEM currently tries to allocate each section's page extensions
> from the buddy allocator before falling back to vmalloc. Boot-time
> section allocation happens after vmalloc is available, and memory
> hotplug allocations do not require physically contiguous backing.
>
> Use vzalloc_node() directly and remove the buddy-specific allocation,
> free, and kmemleak bookkeeping. This leaves one runtime backing type
> and lets a later change add memblock as the distinct boot-time path
> to simplify the code.
>
> Signed-off-by: Muchun Song <songmuchun@xxxxxxxxxxxxx>

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

> ---
> v2:
> - Add a preparatory cleanup that always uses vmalloc for SPARSEMEM
> section page extensions (suggested by Mike Rapoport)
> ---
> mm/page_ext.c | 21 +++------------------
> 1 file changed, 3 insertions(+), 18 deletions(-)

--
Sincerely yours,
Mike.