On 2024-12-10 02:47, Andrew Morton wrote:
------------------------------------------------------
From: David Hildenbrand <david@xxxxxxxxxx>
Subject: mm/page_alloc: don't use __GFP_HARDWALL when migrating pages
via alloc_contig*()
Date: Thu, 5 Dec 2024 10:05:07 +0100
Patch series "mm: don't use __GFP_HARDWALL when migrating remote
pages".
__GFP_HARDWALL means that we will be respecting the cpuset of the
caller
when allocating a page. However, when we are migrating remote
allocations
(pages allocated from other context), the cpuset of the current context
is
irrelevant.
For memory offlining + alloc_contig_*(), this is rather obvious. There
might be other such page migration users, let's start with the obvious
ones.
This patch (of 2):
We'll migrate pages allocated by other contexts; respecting the cpuset
of
the alloc_contig*() caller when allocating a migration target does not
make sense.
Drop the __GFP_HARDWALL.
Note that in an ideal world, migration code could figure out the cpuset
of the original context and take that into consideration.
Link:
https://lkml.kernel.org/r/20241205090508.2095225-1-david@xxxxxxxxxx
Link:
https://lkml.kernel.org/r/20241205090508.2095225-2-david@xxxxxxxxxx
Signed-off-by: David Hildenbrand <david@xxxxxxxxxx>
Suggested-by: Vlastimil Babka <vbabka@xxxxxxx>
Reviewed-by: Vlastimil Babka <vbabka@xxxxxxx>
Cc: Oscar Salvador <osalvador@xxxxxxx>
Cc: Zi Yan <ziy@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Same here:
Reviewed-by: Oscar Salvador <osalvador@xxxxxxx>
--
Oscar Salvador
SUSE Labs
