From: osalvador <osalvador@suse.de>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: Michal Hocko <mhocko@suse.com>,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm, hotplug: protect nr_zones with pgdat_resize_lock()
Date: Wed, 21 Nov 2018 09:24:14 +0100 [thread overview]
Message-ID: <1542788654.2940.14.camel@suse.de> (raw)
In-Reply-To: <20181121025231.ggk7zgq53nmqsqds@master>
On Wed, 2018-11-21 at 02:52 +0000, Wei Yang wrote:
> On Tue, Nov 20, 2018 at 08:58:11AM +0100, osalvador@suse.de wrote:
> > > On the other hand I would like to see the global lock to go away
> > > because
> > > it causes scalability issues and I would like to change it to a
> > > range
> > > lock. This would make this race possible.
> > >
> > > That being said this is more of a preparatory work than a fix.
> > > One could
> > > argue that pgdat resize lock is abused here but I am not
> > > convinced a
> > > dedicated lock is much better. We do take this lock already and
> > > spanning
> > > its scope seems reasonable. An update to the documentation is
> > > due.
> >
> > Would not make more sense to move it within the pgdat lock
> > in move_pfn_range_to_zone?
> > The call from free_area_init_core is safe as we are single-thread
> > there.
> >
>
> Agree. This would be better.
>
> > And if we want to move towards a range locking, I even think it
> > would be more
> > consistent if we move it within the zone's span lock (which is
> > already
> > wrapped with a pgdat lock).
> >
>
> I lost a little here, just want to confirm with you.
>
> Instead of call pgdat_resize_lock() around
> init_currently_empty_zone()
> in move_pfn_range_to_zone(), we move init_currently_empty_zone()
> before
> resize_zone_range()?
>
> This sounds reasonable.
Yeah.
spanned pages are being touched in:
- shrink_pgdat_span
- resize_zone_range
- init_currently_emty_zone
The first two are already protected by the span lock.
In init_currently_empty_zone, we also touch zone_start_pfn, which is
part of the spanned pages (beginning), so I think it makes sense to
also protect it with the span lock.
We just call init_currently_empty_zone in case the zone is empty, so
the race should be not existent to be honest.
But I just think it is more consistent, and since moving it under
spanlock would imply to also have it under pgdat lock, which was the
main point of this, I think we do not have anything to lose.
next prev parent reply other threads:[~2018-11-21 8:24 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 [this message]
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 ` [PATCH v4] " Wei Yang
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=1542788654.2940.14.camel@suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=richard.weiyang@gmail.com \
/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.