From: Joel Fernandes <joel@joelfernandes.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Marco Elver <elver@google.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
"Uladzislau Rezki (Sony)" <urezki@gmail.com>,
fweisbec@gmail.com, neeraj.iitr10@gmail.com
Subject: Re: [PATCH v8 2/6] rcu/segcblist: Add counters to segcblist datastructure
Date: Mon, 26 Oct 2020 01:45:57 -0400 [thread overview]
Message-ID: <20201026054557.GB4192074@google.com> (raw)
In-Reply-To: <20201026005058.GB104441@lothringen>
On Mon, Oct 26, 2020 at 01:50:58AM +0100, Frederic Weisbecker wrote:
> On Wed, Oct 21, 2020 at 03:08:09PM -0400, Joel Fernandes (Google) wrote:
> > bool rcu_segcblist_accelerate(struct rcu_segcblist *rsclp, unsigned long seq)
> > {
> > - int i;
> > + int i, j;
> >
> > WARN_ON_ONCE(!rcu_segcblist_is_enabled(rsclp));
> > if (rcu_segcblist_restempty(rsclp, RCU_DONE_TAIL))
> > @@ -487,6 +508,10 @@ bool rcu_segcblist_accelerate(struct rcu_segcblist *rsclp, unsigned long seq)
> > if (rcu_segcblist_restempty(rsclp, i) || ++i >= RCU_NEXT_TAIL)
> > return false;
> >
> > + /* Accounting: everything below i is about to get merged into i. */
> > + for (j = i + 1; j <= RCU_NEXT_TAIL; j++)
> > + rcu_segcblist_move_seglen(rsclp, j, i);
> > +
>
> Can you perhaps reuse the below loop to move the seglen?
Not easily, because we will need to store 'i' into another variable then, which
does not change.
Besides IMHO, the code is more readable with the loops separated.
thanks,
- Joel
> > /*
> > * Merge all later callbacks, including newly arrived callbacks,
> > * into the segment located by the for-loop above. Assign "seq"
next prev parent reply other threads:[~2020-10-26 5:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 19:08 [PATCH v8 0/6] Add support for length of each segment in the segcblist Joel Fernandes (Google)
2020-10-21 19:08 ` [PATCH v8 1/6] rcu/tree: Make rcu_do_batch count how many callbacks were executed Joel Fernandes (Google)
2020-10-21 19:08 ` [PATCH v8 2/6] rcu/segcblist: Add counters to segcblist datastructure Joel Fernandes (Google)
2020-10-26 0:32 ` Frederic Weisbecker
2020-10-26 5:40 ` Joel Fernandes
2020-10-26 11:24 ` Frederic Weisbecker
2020-10-27 17:30 ` Joel Fernandes
2020-10-26 0:50 ` Frederic Weisbecker
2020-10-26 5:45 ` Joel Fernandes [this message]
2020-10-26 11:28 ` Frederic Weisbecker
2020-10-21 19:08 ` [PATCH v8 3/6] rcu/trace: Add tracing for how segcb list changes Joel Fernandes (Google)
2020-10-26 11:59 ` Frederic Weisbecker
2020-11-03 13:47 ` Joel Fernandes
2020-11-05 3:37 ` Paul E. McKenney
2020-10-21 19:08 ` [PATCH v8 4/6] rcu/segcblist: Remove useless rcupdate.h include Joel Fernandes (Google)
2020-10-21 19:08 ` [PATCH v8 5/6] rcu/tree: segcblist: Remove redundant smp_mb()s Joel Fernandes (Google)
2020-10-26 12:01 ` Frederic Weisbecker
2020-10-21 19:08 ` [PATCH v8 6/6] rcu/segcblist: Add additional comments to explain smp_mb() Joel Fernandes (Google)
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=20201026054557.GB4192074@google.com \
--to=joel@joelfernandes.org \
--cc=elver@google.com \
--cc=frederic@kernel.org \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.iitr10@gmail.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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