[PATCH v3 4/5] kho: fix bootmem sizing
sashiko-bot at kernel.org
sashiko-bot at kernel.org
Thu Nov 12 02:47:52 PST 2026
> Bootmem areas are sized from overlapping views of the memory reserved in
> memblock:
>
> * the global area is sized from all reserved memory, including memory
> allocated on specific nodes, so on NUMA systems everything allocated
> on a node is accounted in both the global area and the area of that
> node.
> * per-node sizes are calculated after the lowmem and the global areas
> are reserved. With CONFIG_NUMA=n all memblock regions belong to node 0,
> so the lowmem and the global areas are accounted in the size of node 0
> area and scaled once again.
>
> As a result, bootmem is about twice bigger than it should be on NUMA
> systems and about four times bigger with CONFIG_NUMA=n. On small systems
> reservation of the bootmem may fail and then KHO gets disabled.
> [ ... ]
> Reviewed-by: Pasha Tatashin <pasha.tatashin at soleen.com>
> Reviewed-by: Jose A. Perez de Azpillaga <azpijr at gmail.com>
> Reviewed-by: Pratyush Yadav <pratyush at kernel.org>
> Reviewed-by: Mukesh Pilaniya <mpilaniy at redhat.com>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt at kernel.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112-kho-bootmem-sizing-v3-0-f0c8d00295d5@kernel.org?part=4
More information about the kexec
mailing list