[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190408082633.2864-1-osalvador@suse.de>
Date: Mon, 8 Apr 2019 10:26:31 +0200
From: Oscar Salvador <osalvador@...e.de>
To: akpm@...ux-foundation.org
Cc: mhocko@...e.com, david@...hat.com, dan.j.williams@...el.com,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Oscar Salvador <osalvador@...e.de>
Subject: [PATCH v2 0/2] Preparing memhotplug for allocating memmap from hot-added range
v1 -> v2: Added David's feedback and his Reviewed-by
Hi,
these patches were posted as part of patchset [1], but it was agreed that
patch#3 must be further discussed.
Whole discussion can be seen in the cover letter.
But the first two patches make sense by themselves, as the first one is a nice
code cleanup, and the second one sets up the interface that the feature implemented
in [1] will use.
We decided to go this way because there are other people working on the same area,
and conflicts can arise easily, so better merge it now.
Also, it is safe as they do not implement any functional changes.
[1] https://patchwork.kernel.org/cover/10875017/
Michal Hocko (2):
mm, memory_hotplug: cleanup memory offline path
mm, memory_hotplug: provide a more generic restrictions for memory
hotplug
arch/arm64/mm/mmu.c | 6 ++---
arch/ia64/mm/init.c | 6 ++---
arch/powerpc/mm/mem.c | 6 ++---
arch/s390/mm/init.c | 6 ++---
arch/sh/mm/init.c | 6 ++---
arch/x86/mm/init_32.c | 6 ++---
arch/x86/mm/init_64.c | 10 ++++----
include/linux/memory_hotplug.h | 32 ++++++++++++++++++------
kernel/memremap.c | 12 ++++++---
mm/memory_hotplug.c | 56 ++++++++++++++----------------------------
mm/page_alloc.c | 11 +++++++--
11 files changed, 84 insertions(+), 73 deletions(-)
--
2.13.7
Powered by blists - more mailing lists