From: Frederic Weisbecker <frederic@kernel.org>
To: Boqun Feng <boqun.feng@gmail.com>
Cc: Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RFC 0/2] srcu: Remove pre-flip memory barrier
Date: Wed, 21 Dec 2022 18:30:05 +0100 [thread overview]
Message-ID: <20221221173005.GB37362@lothringen> (raw)
In-Reply-To: <Y6MuFH2ZMY7mV06q@Boquns-Mac-mini.local>
On Wed, Dec 21, 2022 at 08:02:28AM -0800, Boqun Feng wrote:
> On Wed, Dec 21, 2022 at 12:26:29PM +0100, Frederic Weisbecker wrote:
> > On Tue, Dec 20, 2022 at 09:41:17PM -0500, Joel Fernandes wrote:
> > >
> > >
> > > > On Dec 20, 2022, at 7:50 PM, Frederic Weisbecker <frederic@kernel.org> wrote:
> > > >
> > > > On Tue, Dec 20, 2022 at 07:15:00PM -0500, Joel Fernandes wrote:
> > > >> On Tue, Dec 20, 2022 at 5:45 PM Frederic Weisbecker <frederic@kernel.org> wrote:
> > > >> Agreed about (1).
> > > >>
> > > >>> _ In (2), E pairs with the address-dependency between idx and lock_count.
> > > >>
> > > >> But that is not the only reason. If that was the only reason for (2),
> > > >> then there is an smp_mb() just before the next-scan post-flip before
> > > >> the lock counts are read.
> > > >
> > > > The post-flip barrier makes sure the new idx is visible on the next READER's
> > > > turn, but it doesn't protect against the fact that "READ idx then WRITE lock[idx]"
> > > > may appear unordered from the update side POV if there is no barrier between the
> > > > scan and the flip.
> > > >
> > > > If you remove the smp_mb() from the litmus test I sent, things explode.
> > >
> > > Sure I see what you are saying and it’s a valid point as well. However why do you need memory barrier D (labeled such in the kernel code) for that? You already have a memory barrier A before the lock count is read. That will suffice for the ordering pairing with the addr dependency.
> > > In other words, if updater sees readers lock counts, then reader would be making those lock count updates on post-flip inactive index, not the one being scanned as you wanted, and you will accomplish that just with the mem barrier A.
> > >
> > > So D fixes the above issue you are talking about (lock count update), however that is already fixed by the memory barrier A. But you still need D for the issue I mentioned (unlock counts vs flip).
> > >
> > > That’s just my opinion and let’s discuss more because I cannot rule out that I
> > > am missing something with this complicated topic ;-)
> >
> > I must be missing something. I often do.
> >
> > Ok let's put that on litmus:
> >
> > ----
> > C srcu
> >
> > {}
> >
> > // updater
> > P0(int *IDX, int *LOCK0, int *UNLOCK0, int *LOCK1, int *UNLOCK1)
> > {
> > int lock1;
> > int unlock1;
> > int lock0;
> > int unlock0;
> >
> > // SCAN1
> > unlock1 = READ_ONCE(*UNLOCK1);
> > smp_mb(); // A
> > lock1 = READ_ONCE(*LOCK1);
> >
> > // FLIP
> > smp_mb(); // E
>
> In real code there is a control dependency between the READ_ONCE() above
> and the WRITE_ONCE() before, i.e. only flip the idx when lock1 ==
> unlock1, maybe try with the P0 below? Untested due to not having herd on
> this computer ;-)
>
> > WRITE_ONCE(*IDX, 1);
> > smp_mb(); // D
> >
> > // SCAN2
> > unlock0 = READ_ONCE(*UNLOCK0);
> > smp_mb(); // A
> > lock0 = READ_ONCE(*LOCK0);
> > }
> >
> P0(int *IDX, int *LOCK0, int *UNLOCK0, int *LOCK1, int *UNLOCK1)
> {
> int lock1;
> int unlock1;
> int lock0;
> int unlock0;
>
> // SCAN1
> unlock1 = READ_ONCE(*UNLOCK1);
> smp_mb(); // A
> lock1 = READ_ONCE(*LOCK1);
>
> // FLIP
> if (unlock1 == lock1) {
> smp_mb(); // E
> WRITE_ONCE(*IDX, 1);
> smp_mb(); // D
>
> // SCAN2
> unlock0 = READ_ONCE(*UNLOCK0);
> smp_mb(); // A
> lock0 = READ_ONCE(*LOCK0);
> }
> }
That becomes the below (same effect).
C D
{}
// updater
P0(int *IDX, int *LOCK0, int *UNLOCK0, int *LOCK1, int *UNLOCK1)
{
int lock1;
int unlock1;
int lock0;
int unlock0;
// SCAN1
unlock1 = READ_ONCE(*UNLOCK1);
smp_mb(); // A
lock1 = READ_ONCE(*LOCK1);
if (unlock1 == lock1) {
// FLIP
smp_mb(); // E
WRITE_ONCE(*IDX, 1);
smp_mb(); // D
// SCAN 2
unlock0 = READ_ONCE(*UNLOCK0);
smp_mb(); // A
lock0 = READ_ONCE(*LOCK0);
}
}
// reader
P1(int *IDX, int *LOCK0, int *UNLOCK0, int *LOCK1, int *UNLOCK1)
{
int tmp;
int idx;
// 1st reader
idx = READ_ONCE(*IDX);
if (idx == 0) {
tmp = READ_ONCE(*LOCK0);
WRITE_ONCE(*LOCK0, tmp + 1);
smp_mb(); /* B and C */
tmp = READ_ONCE(*UNLOCK0);
WRITE_ONCE(*UNLOCK0, tmp + 1);
} else {
tmp = READ_ONCE(*LOCK1);
WRITE_ONCE(*LOCK1, tmp + 1);
smp_mb(); /* B and C */
tmp = READ_ONCE(*UNLOCK1);
WRITE_ONCE(*UNLOCK1, tmp + 1);
}
// second reader
idx = READ_ONCE(*IDX);
if (idx == 0) {
tmp = READ_ONCE(*LOCK0);
WRITE_ONCE(*LOCK0, tmp + 1);
smp_mb(); /* B and C */
tmp = READ_ONCE(*UNLOCK0);
WRITE_ONCE(*UNLOCK0, tmp + 1);
} else {
tmp = READ_ONCE(*LOCK1);
WRITE_ONCE(*LOCK1, tmp + 1);
smp_mb(); /* B and C */
tmp = READ_ONCE(*UNLOCK1);
WRITE_ONCE(*UNLOCK1, tmp + 1);
}
// third reader
idx = READ_ONCE(*IDX);
if (idx == 0) {
tmp = READ_ONCE(*LOCK0);
WRITE_ONCE(*LOCK0, tmp + 1);
smp_mb(); /* B and C */
tmp = READ_ONCE(*UNLOCK0);
WRITE_ONCE(*UNLOCK0, tmp + 1);
} else {
tmp = READ_ONCE(*LOCK1);
WRITE_ONCE(*LOCK1, tmp + 1);
smp_mb(); /* B and C */
tmp = READ_ONCE(*UNLOCK1);
WRITE_ONCE(*UNLOCK1, tmp + 1);
}
}
exists (0:unlock0=0 /\ 1:idx=0)
next prev parent reply other threads:[~2022-12-21 17:30 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 19:13 [RFC 0/2] srcu: Remove pre-flip memory barrier Joel Fernandes (Google)
2022-12-18 19:13 ` [RFC 1/2] srcu: Remove comment about prior read lock counts Joel Fernandes (Google)
2022-12-18 21:08 ` Mathieu Desnoyers
2022-12-18 21:19 ` Joel Fernandes
2022-12-18 19:13 ` [RFC 2/2] srcu: Remove memory barrier "E" as it is not required Joel Fernandes (Google)
2022-12-18 21:42 ` Frederic Weisbecker
2022-12-18 23:26 ` Joel Fernandes
2022-12-19 0:30 ` Joel Fernandes
2022-12-18 20:57 ` [RFC 0/2] srcu: Remove pre-flip memory barrier Mathieu Desnoyers
2022-12-18 21:30 ` Joel Fernandes
2022-12-18 23:26 ` Paul E. McKenney
2022-12-18 23:38 ` Mathieu Desnoyers
2022-12-19 0:04 ` Joel Fernandes
2022-12-19 0:24 ` Joel Fernandes
2022-12-19 1:50 ` Mathieu Desnoyers
2022-12-20 0:55 ` Joel Fernandes
2022-12-20 1:04 ` Joel Fernandes
2022-12-20 17:00 ` Mathieu Desnoyers
2022-12-20 18:05 ` Joel Fernandes
2022-12-20 18:14 ` Mathieu Desnoyers
2022-12-20 18:29 ` Joel Fernandes
2022-12-20 19:01 ` Mathieu Desnoyers
2022-12-20 19:06 ` Joel Fernandes
2022-12-20 23:05 ` Frederic Weisbecker
2022-12-20 23:46 ` Joel Fernandes
2022-12-21 0:27 ` Frederic Weisbecker
2022-12-20 22:57 ` Frederic Weisbecker
2022-12-21 3:34 ` Mathieu Desnoyers
2022-12-21 11:59 ` Frederic Weisbecker
2022-12-21 17:11 ` Mathieu Desnoyers
2022-12-22 12:40 ` Frederic Weisbecker
2022-12-22 13:19 ` Joel Fernandes
2022-12-22 16:43 ` Paul E. McKenney
2022-12-22 18:19 ` Joel Fernandes
2022-12-22 18:53 ` Paul E. McKenney
2022-12-22 18:56 ` Joel Fernandes
2022-12-22 19:45 ` Paul E. McKenney
2022-12-23 4:43 ` Joel Fernandes
2022-12-23 16:12 ` Joel Fernandes
2022-12-23 18:15 ` Paul E. McKenney
2022-12-23 20:10 ` Joel Fernandes
2022-12-23 20:52 ` Paul E. McKenney
2022-12-20 20:55 ` Joel Fernandes
2022-12-21 3:52 ` Mathieu Desnoyers
2022-12-21 5:02 ` Joel Fernandes
2022-12-21 0:07 ` Frederic Weisbecker
2022-12-21 3:47 ` Mathieu Desnoyers
2022-12-20 4:07 ` Joel Fernandes
2022-12-20 12:34 ` Frederic Weisbecker
2022-12-20 12:40 ` Frederic Weisbecker
2022-12-20 13:44 ` Joel Fernandes
2022-12-20 14:07 ` Frederic Weisbecker
2022-12-20 14:20 ` Joel Fernandes
2022-12-20 22:44 ` Frederic Weisbecker
2022-12-21 0:15 ` Joel Fernandes
2022-12-21 0:49 ` Frederic Weisbecker
2022-12-21 0:58 ` Frederic Weisbecker
2022-12-21 3:43 ` Mathieu Desnoyers
2022-12-21 4:26 ` Joel Fernandes
2022-12-21 14:04 ` Frederic Weisbecker
2022-12-21 16:30 ` Mathieu Desnoyers
2022-12-21 12:11 ` Frederic Weisbecker
2022-12-21 17:20 ` Mathieu Desnoyers
2022-12-21 18:18 ` Joel Fernandes
2022-12-21 2:41 ` Joel Fernandes
2022-12-21 11:26 ` Frederic Weisbecker
2022-12-21 16:02 ` Boqun Feng
2022-12-21 17:30 ` Frederic Weisbecker [this message]
2022-12-21 19:33 ` Joel Fernandes
2022-12-21 19:57 ` Joel Fernandes
2022-12-21 20:19 ` Boqun Feng
2022-12-22 12:16 ` Frederic Weisbecker
2022-12-22 12:24 ` Frederic Weisbecker
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=20221221173005.GB37362@lothringen \
--to=frederic@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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 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.