From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
Michal Hocko <mhocko@suse.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Dan Williams <dan.j.williams@intel.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH v1] mm/memory_hotplug: Don't take the cpu_hotplug_lock
Date: Tue, 24 Sep 2019 16:36:15 +0200 [thread overview]
Message-ID: <20190924143615.19628-1-david@redhat.com> (raw)
Since commit 3f906ba23689 ("mm/memory-hotplug: switch locking to a percpu
rwsem") we do a cpus_read_lock() in mem_hotplug_begin(). This was
introduced to fix a potential deadlock between get_online_mems() and
get_online_cpus() - the memory and cpu hotplug lock. The root issue was
that build_all_zonelists() -> stop_machine() required the cpu hotplug lock:
The reason is that memory hotplug takes the memory hotplug lock and
then calls stop_machine() which calls get_online_cpus(). That's the
reverse lock order to get_online_cpus(); get_online_mems(); in
mm/slub_common.c
So memory hotplug never really required any cpu lock itself, only
stop_machine() and lru_add_drain_all() required it. Back then,
stop_machine_cpuslocked() and lru_add_drain_all_cpuslocked() were used
as the cpu hotplug lock was now obtained in the caller.
Since commit 11cd8638c37f ("mm, page_alloc: remove stop_machine from build
all_zonelists"), the stop_machine_cpuslocked() call is gone.
build_all_zonelists() does no longer require the cpu lock and does no
longer make use of stop_machine().
Since commit 9852a7212324 ("mm: drop hotplug lock from
lru_add_drain_all()"), lru_add_drain_all() "Doesn't need any cpu hotplug
locking because we do rely on per-cpu kworkers being shut down before our
page_alloc_cpu_dead callback is executed on the offlined cpu.". The
lru_add_drain_all_cpuslocked() variant was removed.
So there is nothing left that requires the cpu hotplug lock. The memory
hotplug lock and the device hotplug lock are sufficient.
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Oscar Salvador <osalvador@suse.de>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: David Hildenbrand <david@redhat.com>
---
RFC -> v1:
- Reword and add more details why the cpu hotplug lock was needed here
in the first place, and why we no longer require it.
---
mm/memory_hotplug.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index c3e9aed6023f..5fa30f3010e1 100644
--- a/mm/memory_hotplug.c
+++ b/mm/memory_hotplug.c
@@ -88,14 +88,12 @@ __setup("memhp_default_state=", setup_memhp_default_state);
void mem_hotplug_begin(void)
{
- cpus_read_lock();
percpu_down_write(&mem_hotplug_lock);
}
void mem_hotplug_done(void)
{
percpu_up_write(&mem_hotplug_lock);
- cpus_read_unlock();
}
u64 max_mem_size = U64_MAX;
--
2.21.0
next reply other threads:[~2019-09-24 14:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 14:36 David Hildenbrand [this message]
2019-09-24 14:48 ` [PATCH v1] mm/memory_hotplug: Don't take the cpu_hotplug_lock Michal Hocko
2019-09-24 15:01 ` David Hildenbrand
2019-09-24 15:03 ` Qian Cai
2019-09-24 15:11 ` Michal Hocko
2019-09-24 18:54 ` Qian Cai
2019-09-25 7:02 ` David Hildenbrand
2019-09-25 16:01 ` Qian Cai
2019-09-25 17:48 ` Michal Hocko
2019-09-25 18:20 ` Qian Cai
2019-09-25 19:48 ` David Hildenbrand
2019-09-25 20:32 ` Qian Cai
2019-09-26 7:26 ` David Hildenbrand
2019-09-26 7:38 ` Michal Hocko
2019-09-26 7:26 ` Michal Hocko
2019-09-26 11:19 ` Qian Cai
2019-09-26 11:52 ` Michal Hocko
2019-09-26 13:02 ` Qian Cai
2019-09-26 13:14 ` David Hildenbrand
2019-09-25 10:03 ` Michal Hocko
2019-09-24 15:23 ` David Hildenbrand
2019-10-02 21:37 ` Qian Cai
2019-10-04 7:42 ` David Hildenbrand
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=20190924143615.19628-1-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=tglx@linutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.