Skip to content

mm: don't use __GFP_HARDWALL when migrating remote pages

David Hildenbrand linux-mm lkml 2 versions In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v1 Latest posting 2/22 patches 3 repliesIn review 1 of 2 applied
  2. v1 posting 1/22 patches 6 repliesSuperseded

Patches in v1 posting 2/2 1 of 2 applied

#Subject and filesSizeRepliesApplied
1/2mm/page_alloc: don't use __GFP_HARDWALL when migrating pages via alloc_contig*()mm/page_alloc.c+3 -31 reply
2/2mm/memory_hotplug: don't use __GFP_HARDWALL when migrating pages via memory offliningmm/memory_hotplug.c+1 -11 replyApplied

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchVlastimil Babka
1/2R-b
2/2R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH RESEND v1 0/2] mm: don't use __GFP_HARDWALL when migrating remote pages

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 <[email protected]>
Cc Vlastimil Babka <[email protected]>
Cc Oscar Salvador <[email protected]>
Cc Zi Yan <[email protected]>

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(-)
Signature · 1 line
2.47.1