From: Oscar Salvador <osalvador@suse.de>
To: akpm@linux-foundation.org
Cc: mhocko@suse.com, david@redhat.com, dan.j.williams@intel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Oscar Salvador <osalvador@suse.de>
Subject: [PATCH v2 0/2] Preparing memhotplug for allocating memmap from hot-added range
Date: Mon, 8 Apr 2019 10:26:31 +0200 [thread overview]
Message-ID: <20190408082633.2864-1-osalvador@suse.de> (raw)
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
next reply other threads:[~2019-04-08 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 8:26 Oscar Salvador [this message]
2019-04-08 8:26 ` [PATCH v2 1/2] mm, memory_hotplug: cleanup memory offline path Oscar Salvador
2019-04-08 8:26 ` [PATCH v2 2/2] mm, memory_hotplug: provide a more generic restrictions for memory hotplug Oscar Salvador
2019-04-09 4:30 ` Andrew Morton
2019-04-09 6:12 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190408082633.2864-1-osalvador@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).