Resending via a known-working SMTP setup.
---
__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.
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Cc: Vlastimil Babka <vbabka@xxxxxxx>
Cc: Oscar Salvador <osalvador@xxxxxxx>
Cc: Zi Yan <ziy@xxxxxxxxxx>
David Hildenbrand (2):
mm/page_alloc: don't use __GFP_HARDWALL when migrating pages via
alloc_contig*()
mm/memory_hotplug: don't use __GFP_HARDWALL when migrating pages via
memory offlining
mm/memory_hotplug.c | 2 +-
mm/page_alloc.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.47.1
