public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: Ethan Hansen <1ethanhansen@gmail.com>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
	dave@stgolabs.net, josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	joel@joelfernandes.org
Subject: Re: [PATCH tip/core/rcu 1/1] rcu: Remove unused variable rcu_perf_writer_state
Date: Wed, 7 Aug 2019 16:41:25 -0700	[thread overview]
Message-ID: <20190807234125.GK28441@linux.ibm.com> (raw)
In-Reply-To: <1565220415-3070-1-git-send-email-1ethanhansen@gmail.com>

On Wed, Aug 07, 2019 at 04:26:55PM -0700, Ethan Hansen wrote:
> The variable rcu_perf_writer_state is declared and initialized,
> but is never actually referenced. Remove it to clean code.
> 
> Signed-off-by: Ethan Hansen <1ethanhansen@gmail.com>

Good eyes, thank you!  One question below.

							Thanx, Paul

> ---
>  kernel/rcu/rcuperf.c | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/kernel/rcu/rcuperf.c b/kernel/rcu/rcuperf.c
> index 5a879d0..ff02936 100644
> --- a/kernel/rcu/rcuperf.c
> +++ b/kernel/rcu/rcuperf.c
> @@ -109,7 +109,6 @@
>  static unsigned long b_rcu_perf_writer_finished;
>  static DEFINE_PER_CPU(atomic_t, n_async_inflight);
>  
> -static int rcu_perf_writer_state;
>  #define RTWS_INIT		0
>  #define RTWS_ASYNC		1
>  #define RTWS_BARRIER		2

Does removing this variable also mean that the RTWS_* C preprocessor
macros are now unused?

> @@ -404,25 +403,20 @@ static void rcu_perf_async_cb(struct rcu_head *rhp)
>  			if (!rhp)
>  				rhp = kmalloc(sizeof(*rhp), GFP_KERNEL);
>  			if (rhp && atomic_read(this_cpu_ptr(&n_async_inflight)) < gp_async_max) {
> -				rcu_perf_writer_state = RTWS_ASYNC;
>  				atomic_inc(this_cpu_ptr(&n_async_inflight));
>  				cur_ops->async(rhp, rcu_perf_async_cb);
>  				rhp = NULL;
>  			} else if (!kthread_should_stop()) {
> -				rcu_perf_writer_state = RTWS_BARRIER;
>  				cur_ops->gp_barrier();
>  				goto retry;
>  			} else {
>  				kfree(rhp); /* Because we are stopping. */
>  			}
>  		} else if (gp_exp) {
> -			rcu_perf_writer_state = RTWS_EXP_SYNC;
>  			cur_ops->exp_sync();
>  		} else {
> -			rcu_perf_writer_state = RTWS_SYNC;
>  			cur_ops->sync();
>  		}
> -		rcu_perf_writer_state = RTWS_IDLE;
>  		t = ktime_get_mono_fast_ns();
>  		*wdp = t - *wdp;
>  		i_max = i;
> @@ -463,10 +457,8 @@ static void rcu_perf_async_cb(struct rcu_head *rhp)
>  		rcu_perf_wait_shutdown();
>  	} while (!torture_must_stop());
>  	if (gp_async) {
> -		rcu_perf_writer_state = RTWS_BARRIER;
>  		cur_ops->gp_barrier();
>  	}
> -	rcu_perf_writer_state = RTWS_STOPPING;
>  	writer_n_durations[me] = i_max;
>  	torture_kthread_stopping("rcu_perf_writer");
>  	return 0;
> -- 
> 1.8.3.1
> 

      reply	other threads:[~2019-08-07 23:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 23:26 [PATCH tip/core/rcu 1/1] rcu: Remove unused variable rcu_perf_writer_state Ethan Hansen
2019-08-07 23:41 ` 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=20190807234125.GK28441@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=1ethanhansen@gmail.com \
    --cc=dave@stgolabs.net \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox