RFC mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 11 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mm/memory_hotplug: no need to init new pgdat with node_start_pfnmm/ | +6 | 8 replies | |
| 2/2 | mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCKmm/ mm/ | +10 | 3 replies |
Reviews trailers per patch
All 2 patches have a Reviewed-by or Acked-by.
| Patch | Pankaj Gupta | Mike Rapoport | Michal Hocko |
|---|---|---|---|
| 1/2 | A-b | ||
| 2/2 | A-b | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [PATCH RFC 0/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK
While working on some other cleanups I stumbled over the creation/removal of memblocks in hotplug code and wondered why we still need that. Turns out, we only need that handling with CONFIG_ARCH_KEEP_MEMBLOCK - unless I am missing something important (-> RFC).
I'll be sending out patches to remove CONFIG_ARCH_KEEP_MEMBLOCK on s390x soonish, after finding a way to test them.
Gave it a quick test on x86-64.
David Hildenbrand (2):
mm/memory_hotplug: no need to init new pgdat with node_start_pfn mm/memory_hotplug: handle memblocks only with
CONFIG_ARCH_KEEP_MEMBLOCK
mm/Kconfig | 3 +++ mm/memory_hotplug.c | 28 +++++++++++++--------------- 2 files changed, 16 insertions(+), 15 deletions(-)
Signature · 1 line
2.25.1