Re: [RFC PATCH] mm/memory_hotplug: use public nodes for migration targets

From: David Hildenbrand (Arm)

Date: Mon Sep 14 2026 - 04:47:33 EST


On 9/14/26 09:43, Zimo.Lu wrote:
> do_migrate_range() excludes the source node from node_states[N_MEMORY]
> and adds it back only when the nmask is empty. With private nodes in
> N_MEMORY, this can leave a nonempty nmask containing only private nodes,
> when the system has only one public node and others are private nodes.
> Ordinary migration allocations use the public fallback zonelist, so none
> of those nodes can satisfy the allocation.
>
> Build the nmask from N_MEMORY_PUBLIC so that private nodes do not prevent
> this fallback.
>
> For HugeTLB migration during memory offlining, this also excludes other
> private nodes from the nmask when the source node is private and public
> nodes are present.
>
> Signed-off-by: Zimo.Lu <louis2665573906@xxxxxxxxx>
> Assisted-by: LLM
> ---

This should be discussed in the relevant patch set.

--
Cheers,

David