From: Oscar Salvador <osalvador@techadventures.net>
To: linux-mm@kvack.org
Cc: mhocko@suse.com, dan.j.williams@intel.com,
yasu.isimatu@gmail.com, rppt@linux.vnet.ibm.com,
malat@debian.org, linux-kernel@vger.kernel.org,
pavel.tatashin@microsoft.com, jglisse@redhat.com,
Jonathan.Cameron@huawei.com, rafael@kernel.org, david@redhat.com,
dave.jiang@intel.com
Subject: Re: [RFC PATCH v3 0/5] Do not touch pages/zones during hot-remove path
Date: Mon, 8 Oct 2018 15:56:29 +0200 [thread overview]
Message-ID: <20181008135629.GA10959@techadventures.net> (raw)
In-Reply-To: <20181002150029.23461-1-osalvador@techadventures.net>
On Tue, Oct 02, 2018 at 05:00:24PM +0200, Oscar Salvador wrote:
> Oscar Salvador (5):
> mm/memory_hotplug: Add nid parameter to arch_remove_memory
> mm/memory_hotplug: Create add/del_device_memory functions
> mm/memory_hotplug: Check for IORESOURCE_SYSRAM in
> release_mem_region_adjustable
> mm/memory_hotplug: Move zone/pages handling to offline stage
> mm/memory-hotplug: Rework unregister_mem_sect_under_nodes
>
> arch/ia64/mm/init.c | 6 +-
> arch/powerpc/mm/mem.c | 13 +---
> arch/s390/mm/init.c | 2 +-
> arch/sh/mm/init.c | 6 +-
> arch/x86/mm/init_32.c | 6 +-
> arch/x86/mm/init_64.c | 10 +--
> drivers/base/memory.c | 9 ++-
> drivers/base/node.c | 38 ++--------
> include/linux/memory.h | 2 +-
> include/linux/memory_hotplug.h | 17 +++--
> include/linux/node.h | 7 +-
> kernel/memremap.c | 50 +++++---------
> kernel/resource.c | 15 ++++
> mm/memory_hotplug.c | 153 ++++++++++++++++++++++++++---------------
> mm/sparse.c | 4 +-
> 15 files changed, 169 insertions(+), 169 deletions(-)
>
> --
> 2.13.6
If there are no further comments, I will send this as a patchset without RFC
later this week.
Since [1] already landed in mmotm, I will pull out the dependency for [2], and
change both devm/HMM code.
[1] https://patchwork.kernel.org/cover/10617699/
[2] https://patchwork.kernel.org/cover/10613425/
Thanks
--
Oscar Salvador
SUSE L3
prev parent reply other threads:[~2018-10-08 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 15:00 [RFC PATCH v3 0/5] Do not touch pages/zones during hot-remove path Oscar Salvador
2018-10-02 15:00 ` [RFC PATCH v3 1/5] mm/memory_hotplug: Add nid parameter to arch_remove_memory Oscar Salvador
2018-10-04 9:52 ` David Hildenbrand
2018-10-02 15:00 ` [RFC PATCH v3 2/5] mm/memory_hotplug: Create add/del_device_memory functions Oscar Salvador
2018-10-02 15:00 ` [RFC PATCH v3 3/5] mm/memory_hotplug: Check for IORESOURCE_SYSRAM in release_mem_region_adjustable Oscar Salvador
2018-10-02 15:00 ` [RFC PATCH v3 4/5] mm/memory_hotplug: Move zone/pages handling to offline stage Oscar Salvador
2018-10-02 15:00 ` [RFC PATCH v3 5/5] mm/memory-hotplug: Rework unregister_mem_sect_under_nodes Oscar Salvador
2018-10-08 13:56 ` Oscar Salvador [this message]
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=20181008135629.GA10959@techadventures.net \
--to=osalvador@techadventures.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=malat@debian.org \
--cc=mhocko@suse.com \
--cc=pavel.tatashin@microsoft.com \
--cc=rafael@kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=yasu.isimatu@gmail.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).