From: "Paul E. McKenney" <paulmck@kernel.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: boqun.feng@gmail.com, frederic@kernel.org,
neeraj.iitr10@gmail.com, urezki@gmail.com, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] srcu: Yet more detail for srcu_readers_active_idx_check() comments
Date: Wed, 14 Dec 2022 16:04:33 -0800 [thread overview]
Message-ID: <20221215000433.GD4001@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <CAEXW_YQx78ge_U7asX4YHcsi1EDZSRo_wGN_DJmWnXcAYjHWgQ@mail.gmail.com>
On Wed, Dec 14, 2022 at 11:14:48PM +0000, Joel Fernandes wrote:
> On Wed, Dec 14, 2022 at 11:10 PM Joel Fernandes <joel@joelfernandes.org> wrote:
> >
> > On Wed, Dec 14, 2022 at 11:07 PM Joel Fernandes <joel@joelfernandes.org> wrote:
> > >
> > > On Wed, Dec 14, 2022 at 9:24 PM Paul E. McKenney <paulmck@kernel.org> wrote:
> > > > > I also did not get why you care about readers that come and ago (you
> > > > > mentioned the first reader seeing incorrect idx and the second reader
> > > > > seeing the right flipped one, etc). Those readers are irrelevant
> > > > > AFAICS since they came and went, and need not be waited on , right?.
> > > >
> > > > The comment is attempting to show (among other things) that we don't
> > > > need to care about readers that come and go more than twice during that
> > > > critical interval of time during the counter scans.
> > >
> > > Why do we need to care about readers that come and go even once? Once
> > > they are gone, they have already done an unlock() and their RSCS is
> > > over, so they need to be considered AFAICS.
> > >
> >
> > Aargh, I meant: "so they need to be considered AFAICS".
>
> Trying again: "so they need not be considered AFAICS".
Give or take counter wrap, which can make it appear that still-present
readers have finished.
> Anyway, my 1 year old son is sick so signing off for now. Thanks.
Ouch! I hope he recovers quickly and completely!!!
Thanx, Paul
next prev parent reply other threads:[~2022-12-15 0:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 19:13 Paul E. McKenney
2022-12-14 20:51 ` Joel Fernandes
2022-12-14 21:24 ` Paul E. McKenney
2022-12-14 23:07 ` Joel Fernandes
2022-12-14 23:10 ` Joel Fernandes
2022-12-14 23:14 ` Joel Fernandes
2022-12-15 0:04 ` Paul E. McKenney [this message]
2022-12-15 1:34 ` Joel Fernandes
2022-12-15 1:39 ` Paul E. McKenney
2022-12-15 0:01 ` Paul E. McKenney
2022-12-15 16:54 ` Frederic Weisbecker
2022-12-15 17:08 ` Paul E. McKenney
2022-12-15 17:48 ` Joel Fernandes
2022-12-15 17:58 ` Joel Fernandes
2022-12-15 20:13 ` Paul E. McKenney
2022-12-15 22:13 ` Joel Fernandes
2022-12-15 22:22 ` Joel Fernandes
2022-12-16 1:13 ` Paul E. McKenney
2022-12-16 1:09 ` Paul E. McKenney
2022-12-16 16:32 ` Joel Fernandes
2022-12-16 16:39 ` Joel Fernandes
2022-12-16 16:51 ` Paul E. McKenney
2022-12-16 16:54 ` Joel Fernandes
2022-12-16 17:13 ` Paul E. McKenney
2022-12-17 3:19 ` Joel Fernandes
2022-12-17 3:21 ` Joel Fernandes
2022-12-17 5:15 ` Paul E. McKenney
2022-12-17 6:32 ` Joel Fernandes
2022-12-15 19:58 ` Paul E. McKenney
2022-12-15 20:03 ` Joel Fernandes
2022-12-15 20:33 ` Joel Fernandes
2022-12-15 21:39 ` Paul E. McKenney
2022-12-15 21:42 ` Joel Fernandes
2022-12-15 22:10 ` Paul E. McKenney
2022-12-15 22:16 ` Joel Fernandes
2022-12-15 17:58 ` Frederic Weisbecker
2022-12-15 18:53 ` Paul E. McKenney
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=20221215000433.GD4001@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.iitr10@gmail.com \
--cc=rcu@vger.kernel.org \
--cc=urezki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®