From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Huang Ying <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>,
Andi Kleen <ak@linux.intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Omar Sandoval <osandov@fb.com>,
Paul McKenney <paulmck@kernel.org>, Tejun Heo <tj@kernel.org>,
Will Deacon <will.deacon@arm.com>,
Miaohe Lin <linmiaohe@huawei.com>
Subject: Re: [PATCH] mm, swap: Remove unnecessary smp_rmb() in swap_type_to_swap_info()
Date: Fri, 14 May 2021 16:51:49 -0400 [thread overview]
Message-ID: <20210514205149.hxwcuvlnydxafrcc@oracle.com> (raw)
In-Reply-To: <YJ5nPolKPE6xgVsV@hirez.programming.kicks-ass.net>
On Fri, May 14, 2021 at 02:04:14PM +0200, Peter Zijlstra wrote:
> On Thu, May 13, 2021 at 09:59:46PM -0400, Daniel Jordan wrote:
> > Yes, this does help, I didn't understand why smp_wmb stayed around in
> > the original post.
> >
> > I think the only access smp_store_release() orders is p->type. Wouldn't
> > it be kinda inconsistent to only initialize that one field before
> > publishing when many others would be done at the end of
> > alloc_swap_info() after the fact? p->type doesn't seem special. For
> > instance, get_swap_page_of_type() touches si->lock soon after it calls
> > swap_type_to_swap_info(), so there could be a small window where there's
> > a non-NULL si with an uninitialized lock.
> >
> > It's not as if this is likely to be a problem in practice, it would just
> > make it harder to understand why smp_store_release is there. Maybe all
> > we need is a WRITE_ONCE, or if it's really necessary for certain fields
> > to be set before publication then move them up and explain?
>
> You also care about the zero fill from kvzalloc(). Without the
> smp_store_release() the zero-fill from the memset() might only be
> visible 'late'.
Aha, yes, didn't consider that!
> Unless that also isn't a problem?
No, you're right, we need that for p->flags at least.
next prev parent reply other threads:[~2021-05-14 20:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 6:48 Huang Ying
2021-05-13 8:49 ` Miaohe Lin
2021-05-13 9:54 ` Muchun Song
2021-05-13 11:27 ` Miaohe Lin
2021-05-13 12:34 ` Peter Zijlstra
2021-05-13 12:46 ` Peter Zijlstra
2021-05-14 1:59 ` Daniel Jordan
2021-05-14 4:02 ` Huang, Ying
2021-05-14 20:49 ` Daniel Jordan
2021-05-14 12:04 ` Peter Zijlstra
2021-05-14 20:51 ` Daniel Jordan [this message]
2021-05-14 3:27 ` Huang, Ying
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=20210514205149.hxwcuvlnydxafrcc@oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--cc=dave.hansen@linux.intel.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osandov@fb.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=will.deacon@arm.com \
--cc=ying.huang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox