From: Oscar Salvador <osalvador@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Michal Hocko <mhocko@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Vlastimil Babka <vbabka@suse.cz>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Oscar Salvador <osalvador@suse.de>
Subject: [PATCH v2 0/3] Memory hotplug locking cleanup
Date: Wed, 2 Jun 2021 11:14:54 +0200 [thread overview]
Message-ID: <20210602091457.17772-1-osalvador@suse.de> (raw)
Hi all,
I decided to go one step further and completely rip out zone's span_seqlock
and all related functions, since we should be ok by using {get,put}_online_mems()
on the reader side given that memory-hotplug is the only user fiddling with
those values.
Patch#1 and patch#2 could probably be squashed but I decided to keep them
separated so the intention becomes more clear.
Patch#3 only removes declarations that seem never be used.
Given that this is a much bigger surgery, I decided to drop any Acked-by/
Reviewed-by.
Oscar Salvador (3):
mm,page_alloc: Use {get,put}_online_mems() to get stable zone's values
mm,memory_hotplug: Drop unneeded locking
mm,memory_hotplug: Remove unneeded declarations
include/linux/memory_hotplug.h | 38 --------------------------------------
include/linux/mmzone.h | 23 +++++------------------
mm/memory_hotplug.c | 16 +---------------
mm/page_alloc.c | 15 ++++++---------
4 files changed, 12 insertions(+), 80 deletions(-)
--
2.16.3
next reply other threads:[~2021-06-02 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 9:14 Oscar Salvador [this message]
2021-06-02 9:14 ` [PATCH v2 1/3] mm,page_alloc: Use {get,put}_online_mems() to get stable zone's values Oscar Salvador
2021-06-02 18:37 ` David Hildenbrand
2021-06-02 19:45 ` Oscar Salvador
2021-06-03 8:38 ` Oscar Salvador
2021-06-03 12:45 ` Michal Hocko
2021-06-04 7:41 ` Oscar Salvador
2021-06-07 7:52 ` Oscar Salvador
2021-06-07 8:49 ` David Hildenbrand
2021-06-07 10:23 ` Oscar Salvador
2021-06-08 10:42 ` Oscar Salvador
2021-06-08 15:00 ` David Hildenbrand
2021-06-09 9:42 ` David Hildenbrand
2021-06-07 8:42 ` Michal Hocko
2021-06-03 2:32 ` [mm,page_alloc] [confidence: ] acb5758bf4: BUG:sleeping_function_called_from_invalid_context_at_include/linux/percpu-rwsem.h kernel test robot
2021-06-02 9:14 ` [PATCH v2 2/3] mm,memory_hotplug: Drop unneeded locking Oscar Salvador
2021-06-03 12:52 ` Michal Hocko
2021-06-02 9:14 ` [PATCH v2 3/3] mm,memory_hotplug: Remove unneeded declarations Oscar Salvador
2021-06-02 18:38 ` 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=20210602091457.17772-1-osalvador@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=vbabka@suse.cz \
/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).