From: Wei Yang <richard.weiyang@gmail.com>
To: mhocko@suse.com, osalvador@suse.de, david@redhat.com
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH v4] mm, hotplug: move init_currently_empty_zone() under zone_span_lock protection
Date: Tue, 4 Dec 2018 04:50:16 +0800 [thread overview]
Message-ID: <20181203205016.14123-1-richard.weiyang@gmail.com> (raw)
In-Reply-To: <20181130065847.13714-1-richard.weiyang@gmail.com>
During online_pages phase, pgdat->nr_zones will be updated in case this
zone is empty.
Currently the online_pages phase is protected by the global locks
(device_device_hotplug_lock and mem_hotplug_lock), which ensures there
is no contention during the update of nr_zones.
These global locks introduces scalability issues (especially the second
one), which slow down code relying on get_online_mems(). This is also a
preparation for not having to rely on get_online_mems() but instead some
more fine grained locks.
The patch moves init_currently_empty_zone under both zone_span_writelock
and pgdat_resize_lock because both the pgdat state is changed (nr_zones)
and the zone's start_pfn. Also this patch changes the documentation
of node_size_lock to include the protection of nr_zones.
Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
Acked-by: Michal Hocko <mhocko@suse.com>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
CC: David Hildenbrand <david@redhat.com>
---
v4:
* mention the preparation for improving scalability by David's
comment
v3:
* slightly modify the last paragraph of changelog based on Michal's
comment
v2:
* commit log changes
* modify the code in move_pfn_range_to_zone() instead of in
init_currently_empty_zone()
* pgdat_resize_lock documentation change
---
include/linux/mmzone.h | 7 ++++---
mm/memory_hotplug.c | 5 ++---
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 3d0c472438d2..37d9c5c3faa6 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -635,9 +635,10 @@ typedef struct pglist_data {
#endif
#if defined(CONFIG_MEMORY_HOTPLUG) || defined(CONFIG_DEFERRED_STRUCT_PAGE_INIT)
/*
- * Must be held any time you expect node_start_pfn, node_present_pages
- * or node_spanned_pages stay constant. Holding this will also
- * guarantee that any pfn_valid() stays that way.
+ * Must be held any time you expect node_start_pfn,
+ * node_present_pages, node_spanned_pages or nr_zones stay constant.
+ * Holding this will also guarantee that any pfn_valid() stays that
+ * way.
*
* pgdat_resize_lock() and pgdat_resize_unlock() are provided to
* manipulate node_size_lock without checking for CONFIG_MEMORY_HOTPLUG
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 61972da38d93..f626e7e5f57b 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -742,14 +742,13 @@ void __ref move_pfn_range_to_zone(struct zone *zone, unsigned long start_pfn,
int nid = pgdat->node_id;
unsigned long flags;
- if (zone_is_empty(zone))
- init_currently_empty_zone(zone, start_pfn, nr_pages);
-
clear_zone_contiguous(zone);
/* TODO Huh pgdat is irqsave while zone is not. It used to be like that before */
pgdat_resize_lock(pgdat, &flags);
zone_span_writelock(zone);
+ if (zone_is_empty(zone))
+ init_currently_empty_zone(zone, start_pfn, nr_pages);
resize_zone_range(zone, start_pfn, nr_pages);
zone_span_writeunlock(zone);
resize_pgdat_range(pgdat, start_pfn, nr_pages);
--
2.15.1
prev parent reply other threads:[~2018-12-03 20:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 1:48 [PATCH] mm, hotplug: protect nr_zones with pgdat_resize_lock() Wei Yang
2018-11-20 7:31 ` Michal Hocko
2018-11-20 7:58 ` osalvador
2018-11-20 8:48 ` Michal Hocko
2018-11-21 2:52 ` Wei Yang
2018-11-21 7:15 ` Michal Hocko
2018-11-22 1:52 ` Wei Yang
2018-11-22 8:39 ` Michal Hocko
2018-11-26 2:28 ` Wei Yang
2018-11-26 8:16 ` Michal Hocko
2018-11-26 9:06 ` Wei Yang
2018-11-26 10:03 ` Michal Hocko
2018-11-27 0:18 ` Wei Yang
2018-11-27 3:12 ` Wei Yang
2018-11-27 13:16 ` Michal Hocko
2018-11-27 23:56 ` Wei Yang
2018-11-21 8:24 ` osalvador
2018-11-21 2:44 ` Wei Yang
2018-11-21 7:14 ` Michal Hocko
2018-11-22 10:12 ` [PATCH v2] mm, hotplug: move init_currently_empty_zone() under zone_span_lock protection Wei Yang
2018-11-22 10:15 ` Wei Yang
2018-11-22 10:29 ` Michal Hocko
2018-11-22 14:27 ` Wei Yang
2018-11-22 10:37 ` osalvador
2018-11-22 14:28 ` Wei Yang
2018-11-22 15:26 ` David Hildenbrand
2018-11-22 21:28 ` Wei Yang
2018-11-22 21:53 ` David Hildenbrand
2018-11-22 23:53 ` Wei Yang
2018-11-23 8:42 ` Michal Hocko
2018-11-23 8:46 ` David Hildenbrand
2018-11-26 1:44 ` Wei Yang
2018-11-26 9:24 ` David Hildenbrand
2018-11-27 0:23 ` Wei Yang
2018-11-30 6:58 ` [PATCH v3] " Wei Yang
2018-11-30 9:30 ` David Hildenbrand
2018-12-01 0:27 ` Wei Yang
2018-12-03 10:09 ` David Hildenbrand
2018-12-03 20:37 ` Wei Yang
2018-12-03 20:50 ` Wei Yang [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=20181203205016.14123-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
/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).