From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Byungchul Park <byungchul.park@lge.com>,
jiangshanlai@gmail.com, josh@joshtriplett.org,
mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
kernel-team@lge.com
Subject: Re: [PATCH] srcu: Remove dead code in srcu_gp_end()
Date: Wed, 14 Feb 2018 14:18:41 -0800 [thread overview]
Message-ID: <20180214221841.GT3617@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180214100054.45f525fe@gandalf.local.home>
On Wed, Feb 14, 2018 at 10:00:54AM -0500, Steven Rostedt wrote:
> On Wed, 14 Feb 2018 18:05:24 +0900
> Byungchul Park <byungchul.park@lge.com> wrote:
>
> > Of course, compilers will optimize out a dead code. Anyway, remove
> > any dead code for better readibility.
> >
> > Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> > ---
> > kernel/rcu/srcutree.c | 2 --
> > 1 file changed, 2 deletions(-)
> >
> > diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
> > index 44bc0fa..829453b 100644
> > --- a/kernel/rcu/srcutree.c
> > +++ b/kernel/rcu/srcutree.c
> > @@ -531,7 +531,6 @@ static void srcu_gp_end(struct srcu_struct *sp)
> > unsigned long flags;
> > unsigned long gpseq;
> > int idx;
> > - int idxnext;
>
> Interesting. According to git history, idxnext was never actually used.
Which raises the question of what I intended to do with it. Reviewing
that function didn't activate any memories, though it did point out a
candidate simplification.
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Applied, thank you both!
Thanx, Paul
> -- Steve
>
> > unsigned long mask;
> > struct srcu_data *sdp;
> > struct srcu_node *snp;
> > @@ -555,7 +554,6 @@ static void srcu_gp_end(struct srcu_struct *sp)
> >
> > /* Initiate callback invocation as needed. */
> > idx = rcu_seq_ctr(gpseq) % ARRAY_SIZE(snp->srcu_have_cbs);
> > - idxnext = (idx + 1) % ARRAY_SIZE(snp->srcu_have_cbs);
> > rcu_for_each_node_breadth_first(sp, snp) {
> > spin_lock_irq_rcu_node(snp);
> > cbs = false;
>
prev parent reply other threads:[~2018-02-14 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 9:05 Byungchul Park
2018-02-14 15:00 ` Steven Rostedt
2018-02-14 22:18 ` Paul E. McKenney [this message]
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=20180214221841.GT3617@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=byungchul.park@lge.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome