Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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
Message-Id: <20210602091457.17772-1-osalvador@suse.de>
Precedence: bulk

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