linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v1 0/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK
@ 2020-04-22 15:53 David Hildenbrand
  2020-04-22 15:53 ` [PATCH v1 1/2] mm/memory_hotplug: set node_start_pfn of hotadded pgdat to 0 David Hildenbrand
  2020-04-22 15:53 ` [PATCH v1 2/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK David Hildenbrand
  0 siblings, 2 replies; 3+ messages in thread
From: David Hildenbrand @ 2020-04-22 15:53 UTC (permalink / raw)
  To: linux-kernel
  Cc: linux-mm, David Hildenbrand, Andrew Morton, Anshuman Khandual,
	Baoquan He, Michal Hocko, Michal Hocko, Mike Rapoport,
	Oscar Salvador, Pankaj Gupta

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.

Gave it a quick test on x86-64.

RFC -> v1:
- Added ACKs
- Rephrased subject/description of patch #1
- Use IS_ENABLED() instead of ifdefs in patch #2

David Hildenbrand (2):
  mm/memory_hotplug: set node_start_pfn of hotadded pgdat to 0
  mm/memory_hotplug: handle memblocks only with
    CONFIG_ARCH_KEEP_MEMBLOCK

 mm/Kconfig          |  3 +++
 mm/memory_hotplug.c | 35 ++++++++++++++++-------------------
 2 files changed, 19 insertions(+), 19 deletions(-)

-- 
2.25.3



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-04-22 15:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-22 15:53 [PATCH v1 0/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK David Hildenbrand
2020-04-22 15:53 ` [PATCH v1 1/2] mm/memory_hotplug: set node_start_pfn of hotadded pgdat to 0 David Hildenbrand
2020-04-22 15:53 ` [PATCH v1 2/2] mm/memory_hotplug: handle memblocks only with CONFIG_ARCH_KEEP_MEMBLOCK David Hildenbrand

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).