mm: don't use __GFP_HARDWALL when migrating remote pages
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v1 Latest posting 2/22 patches 3 repliesIn review 1 of 2 applied
- v1 posting 1/22 patches 6 repliesSuperseded
Patches in v1 posting 2/2 1 of 2 applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm/page_alloc: don't use __GFP_HARDWALL when migrating pages via alloc_contig*()mm/ | +3 | 1 reply | |
| 2/2 | mm/memory_hotplug: don't use __GFP_HARDWALL when migrating pages via memory offliningmm/ | +1 | 1 reply | Applied |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Vlastimil Babka |
|---|---|
| 1/2 | R-b |
| 2/2 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
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.
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