Re: [RFC PATCH] mm/sparse: remove sparse_buffer

[David Hildenbrand (Arm)]

On 4/7/26 10:39, Muchun Song wrote:
> The sparse_buffer was originally introduced in commit 9bdac9142407
> ("sparsemem: Put mem map for one node together.") to allocate a
> contiguous block of memory for all memmaps of a NUMA node.
> 
> However, the original commit message did not clearly state the actual
> benefits or the necessity of keeping all memmap areas strictly
> contiguous for a given node.

We don't want the memmap to be scattered around, given that it is one of
the biggest allocations during boot.

It's related to not turning too many memory blocks/sections
un-offlinable I think.

I always imagined that memblock would still keep these allocations close
to each other. Can you verify if that is indeed true?

-- 
Cheers,

David