From: "Paul E. McKenney" <paulmck@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: stern@rowland.harvard.edu, parri.andrea@gmail.com,
will@kernel.org, boqun.feng@gmail.com, npiggin@gmail.com,
dhowells@redhat.com, j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
akiyks@gmail.com, dlustig@nvidia.com, joel@joelfernandes.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
andriin@fb.com
Subject: Re: Some -serious- BPF-related litmus tests
Date: Fri, 22 May 2020 03:56:59 -0700 [thread overview]
Message-ID: <20200522105659.GH2869@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200522094407.GK325280@hirez.programming.kicks-ass.net>
On Fri, May 22, 2020 at 11:44:07AM +0200, Peter Zijlstra wrote:
> On Thu, May 21, 2020 at 05:38:50PM -0700, Paul E. McKenney wrote:
> > Hello!
> >
> > Just wanted to call your attention to some pretty cool and pretty serious
> > litmus tests that Andrii did as part of his BPF ring-buffer work:
> >
> > https://lore.kernel.org/bpf/20200517195727.279322-3-andriin@fb.com/
> >
> > Thoughts?
>
> I find:
>
> smp_wmb()
> smp_store_release()
>
> a _very_ weird construct. What is that supposed to even do?
Indeed, and I asked about that in my review of the patch containing the
code. It -could- make sense if there is a prior read and a later store:
r1 = READ_ONCE(a);
WRITE_ONCE(b, 1);
smp_wmb();
smp_store_release(&c, 1);
WRITE_ONCE(d, 1);
So a->c and b->c is smp_store_release() and b->d is smp_wmb(). But if
there were only stores, the smp_wmb() would suffice. And if there wasn't
the trailing store, smp_store_release() would suffice.
But that would at least want a comment, in my opinion. ;-)
Thanx, Paul
next prev parent reply other threads:[~2020-05-22 10:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 0:38 Some -serious- BPF-related litmus tests Paul E. McKenney
2020-05-22 9:44 ` Peter Zijlstra
2020-05-22 10:56 ` Paul E. McKenney [this message]
2020-05-22 14:36 ` Alan Stern
2020-05-22 17:45 ` Paul E. McKenney
2020-05-22 14:32 ` Alan Stern
2020-05-22 14:32 ` Alan Stern
2020-05-22 17:43 ` Paul E. McKenney
2020-05-22 17:43 ` Paul E. McKenney
2020-05-22 19:38 ` Andrii Nakryiko
2020-05-24 12:09 ` Akira Yokosawa
2020-05-24 12:09 ` Akira Yokosawa
2020-05-25 18:31 ` Andrii Nakryiko
2020-05-25 22:01 ` Akira Yokosawa
2020-05-25 23:31 ` Andrii Nakryiko
2020-05-26 10:50 ` Akira Yokosawa
2020-05-26 14:02 ` Akira Yokosawa
2020-05-26 20:19 ` Andrii Nakryiko
2020-05-26 23:00 ` Akira Yokosawa
2020-05-27 0:09 ` Andrii Nakryiko
2020-05-26 20:15 ` Andrii Nakryiko
2020-05-26 22:23 ` Akira Yokosawa
2020-05-25 11:25 ` Peter Zijlstra
2020-05-25 15:47 ` Paul E. McKenney
2020-05-25 15:47 ` Paul E. McKenney
2020-05-25 17:02 ` Peter Zijlstra
2020-05-25 17:21 ` Paul E. McKenney
2020-05-25 17:45 ` Paul E. McKenney
2020-05-28 22:00 ` Joel Fernandes
2020-05-28 22:16 ` Peter Zijlstra
2020-05-29 5:14 ` Andrii Nakryiko
2020-05-29 12:36 ` Peter Zijlstra
2020-05-29 20:01 ` Andrii Nakryiko
2020-05-29 20:53 ` Peter Zijlstra
2020-05-25 14:53 ` Boqun Feng
2020-05-25 14:53 ` Boqun Feng
2020-05-25 18:38 ` Andrii Nakryiko
2020-05-28 21:48 ` Joel Fernandes
2020-05-29 4:38 ` Andrii Nakryiko
2020-05-29 4:38 ` Andrii Nakryiko
2020-05-29 17:23 ` Joel Fernandes
2020-05-29 20:10 ` Andrii Nakryiko
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=20200522105659.GH2869@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=andriin@fb.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@kernel.org \
/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