From: Oscar Salvador <osalvador@suse.de>
To: akpm@linux-foundation.org
Cc: mhocko@suse.com, dan.j.williams@intel.com,
pavel.tatashin@microsoft.com, jglisse@redhat.com,
Jonathan.Cameron@huawei.com, rafael@kernel.org, david@redhat.com,
linux-mm@kvack.org, Oscar Salvador <osalvador@suse.com>
Subject: [PATCH v2 0/5] Do not touch pages in hot-remove path
Date: Tue, 27 Nov 2018 17:20:00 +0100 [thread overview]
Message-ID: <20181127162005.15833-1-osalvador@suse.de> (raw)
From: Oscar Salvador <osalvador@suse.com>
This patchset is based on Dan's HMM/devm refactorization [1].
----
This patchset aims for two things:
1) A better definition about offline and hot-remove stage
2) Solving bugs where we can access non-initialized pages
during hot-remove operations [2] [3].
This is achieved by moving all page/zone handling to the offline
stage, so we do not need to access pages when hot-removing memory.
[1] https://patchwork.kernel.org/cover/10691415/
[2] https://patchwork.kernel.org/patch/10547445/
[3] https://www.spinics.net/lists/linux-mm/msg161316.html
Oscar Salvador (5):
mm, memory_hotplug: Add nid parameter to arch_remove_memory
kernel, resource: 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
mm, memory_hotplug: Refactor shrink_zone/pgdat_span
arch/ia64/mm/init.c | 2 +-
arch/powerpc/mm/mem.c | 14 +--
arch/s390/mm/init.c | 2 +-
arch/sh/mm/init.c | 6 +-
arch/x86/mm/init_32.c | 5 +-
arch/x86/mm/init_64.c | 11 +-
drivers/base/memory.c | 9 +-
drivers/base/node.c | 39 +------
include/linux/memory.h | 2 +-
include/linux/memory_hotplug.h | 12 +-
include/linux/node.h | 9 +-
kernel/memremap.c | 19 ++-
kernel/resource.c | 15 +++
mm/memory_hotplug.c | 254 +++++++++++++++++++----------------------
mm/sparse.c | 4 +-
15 files changed, 182 insertions(+), 221 deletions(-)
--
2.13.6
next reply other threads:[~2018-11-27 16:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 16:20 Oscar Salvador [this message]
2018-11-27 16:20 ` [PATCH v2 1/5] mm, memory_hotplug: Add nid parameter to arch_remove_memory Oscar Salvador
2018-11-27 16:20 ` [PATCH v2 2/5] kernel, resource: Check for IORESOURCE_SYSRAM in release_mem_region_adjustable Oscar Salvador
2018-11-27 16:20 ` [PATCH v2 3/5] mm, memory_hotplug: Move zone/pages handling to offline stage Oscar Salvador
2018-11-28 7:52 ` Mike Rapoport
2018-11-28 14:25 ` osalvador
2018-11-28 14:15 ` osalvador
2018-11-27 16:20 ` [PATCH v2 4/5] mm, memory-hotplug: Rework unregister_mem_sect_under_nodes Oscar Salvador
2019-03-24 6:48 ` Anshuman Khandual
2019-03-25 7:40 ` Oscar Salvador
2019-03-25 8:04 ` Michal Hocko
2019-03-25 8:14 ` Oscar Salvador
2018-11-27 16:20 ` [PATCH v2 5/5] mm, memory_hotplug: Refactor shrink_zone/pgdat_span Oscar Salvador
2018-11-28 6:50 ` Michal Hocko
2018-11-28 7:07 ` Oscar Salvador
2018-11-28 10:03 ` David Hildenbrand
2018-11-28 10:14 ` Michal Hocko
2018-11-28 11:00 ` osalvador
2018-11-28 12:31 ` Michal Hocko
2018-11-28 12:51 ` osalvador
2018-11-28 13:08 ` Michal Hocko
2018-11-28 13:18 ` osalvador
2018-11-28 15:50 ` Michal Hocko
2018-11-28 16:02 ` osalvador
2018-11-29 9:29 ` osalvador
2018-11-28 13:09 ` osalvador
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=20181127162005.15833-1-osalvador@suse.de \
--to=osalvador@suse.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=jglisse@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.com \
--cc=pavel.tatashin@microsoft.com \
--cc=rafael@kernel.org \
/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