From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: cl@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
mingo@elte.hu, rusty@rustcorp.com.au, davem@davemloft.net
Subject: Re: [this_cpu_xx 11/11] RCU: Use this_cpu operations
Date: Wed, 10 Jun 2009 10:42:18 -0700 [thread overview]
Message-ID: <20090610174218.GP6773@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090605191852.373830111@gentwo.org>
On Fri, Jun 05, 2009 at 03:18:30PM -0400, cl@linux-foundation.org wrote:
> RCU does not do dynamic allocations but it increments per cpu variables
> a lot. These instructions results in a move to a register and then back
> to memory. This patch will make it use the inc/dec instructions on x86
> that do not need a register.
Looks good to me!
Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Signed-off-by: Christoph Lameter <cl@linux-foundation.org>
>
> ---
> kernel/rcupreempt.c | 4 ++--
> kernel/rcutorture.c | 8 ++++----
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> Index: linux-2.6/kernel/rcutorture.c
> ===================================================================
> --- linux-2.6.orig/kernel/rcutorture.c 2009-06-04 14:26:42.000000000 -0500
> +++ linux-2.6/kernel/rcutorture.c 2009-06-04 14:38:05.000000000 -0500
> @@ -709,13 +709,13 @@ static void rcu_torture_timer(unsigned l
> /* Should not happen, but... */
> pipe_count = RCU_TORTURE_PIPE_LEN;
> }
> - ++__get_cpu_var(rcu_torture_count)[pipe_count];
> + __this_cpu_inc(per_cpu_var(rcu_torture_count)[pipe_count]);
> completed = cur_ops->completed() - completed;
> if (completed > RCU_TORTURE_PIPE_LEN) {
> /* Should not happen, but... */
> completed = RCU_TORTURE_PIPE_LEN;
> }
> - ++__get_cpu_var(rcu_torture_batch)[completed];
> + __this_cpu_inc(per_cpu_var(rcu_torture_batch)[completed]);
> preempt_enable();
> cur_ops->readunlock(idx);
> }
> @@ -764,13 +764,13 @@ rcu_torture_reader(void *arg)
> /* Should not happen, but... */
> pipe_count = RCU_TORTURE_PIPE_LEN;
> }
> - ++__get_cpu_var(rcu_torture_count)[pipe_count];
> + __this_cpu_inc(per_cpu_var(rcu_torture_count)[pipe_count]);
> completed = cur_ops->completed() - completed;
> if (completed > RCU_TORTURE_PIPE_LEN) {
> /* Should not happen, but... */
> completed = RCU_TORTURE_PIPE_LEN;
> }
> - ++__get_cpu_var(rcu_torture_batch)[completed];
> + __this_cpu_inc(per_cpu_var(rcu_torture_batch)[completed]);
> preempt_enable();
> cur_ops->readunlock(idx);
> schedule();
> Index: linux-2.6/kernel/rcupreempt.c
> ===================================================================
> --- linux-2.6.orig/kernel/rcupreempt.c 2009-06-04 14:28:53.000000000 -0500
> +++ linux-2.6/kernel/rcupreempt.c 2009-06-04 14:39:35.000000000 -0500
> @@ -173,7 +173,7 @@ void rcu_enter_nohz(void)
> static DEFINE_RATELIMIT_STATE(rs, 10 * HZ, 1);
>
> smp_mb(); /* CPUs seeing ++ must see prior RCU read-side crit sects */
> - __get_cpu_var(rcu_dyntick_sched).dynticks++;
> + __this_cpu_inc(per_cpu_var(rcu_dyntick_sched).dynticks);
> WARN_ON_RATELIMIT(__get_cpu_var(rcu_dyntick_sched).dynticks & 0x1, &rs);
> }
>
> @@ -181,7 +181,7 @@ void rcu_exit_nohz(void)
> {
> static DEFINE_RATELIMIT_STATE(rs, 10 * HZ, 1);
>
> - __get_cpu_var(rcu_dyntick_sched).dynticks++;
> + __this_cpu_inc(per_cpu_var(rcu_dyntick_sched).dynticks);
> smp_mb(); /* CPUs seeing ++ must see later RCU read-side crit sects */
> WARN_ON_RATELIMIT(!(__get_cpu_var(rcu_dyntick_sched).dynticks & 0x1),
> &rs);
>
> --
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2009-06-10 17:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 19:18 [this_cpu_xx 00/11] Introduce this_cpu_xx operations cl
2009-06-05 19:18 ` [this_cpu_xx 01/11] Introduce this_cpu_ptr() and generic this_cpu_* operations cl
2009-06-10 5:12 ` Tejun Heo
2009-06-11 15:10 ` Christoph Lameter
2009-06-12 2:09 ` Tejun Heo
2009-06-12 14:18 ` Christoph Lameter
2009-06-17 8:09 ` Tejun Heo
2009-06-17 8:19 ` Tejun Heo
2009-06-17 18:41 ` Christoph Lameter
2009-06-18 1:08 ` Tejun Heo
2009-06-18 3:01 ` Rusty Russell
2009-06-05 19:18 ` [this_cpu_xx 02/11] Use this_cpu operations for SNMP statistics cl
2009-06-05 19:18 ` [this_cpu_xx 03/11] Use this_cpu operations for NFS statistics cl
2009-06-05 19:18 ` [this_cpu_xx 04/11] Use this_cpu ops for network statistics cl
2009-06-08 11:27 ` Robin Holt
2009-06-08 20:49 ` Christoph Lameter
2009-06-08 20:54 ` Ingo Molnar
2009-06-05 19:18 ` [this_cpu_xx 05/11] this_cpu_ptr: Straight transformations cl
2009-06-05 19:18 ` [this_cpu_xx 06/11] Eliminate get/put_cpu cl
2009-06-05 19:34 ` Dan Williams
2009-06-09 14:02 ` Sosnowski, Maciej
2009-06-05 19:18 ` [this_cpu_xx 07/11] xfs_icsb_modify_counters does not need "cpu" variable cl
2009-06-05 19:22 ` Christoph Hellwig
2009-06-05 19:36 ` Christoph Lameter
2009-06-05 19:18 ` [this_cpu_xx 08/11] Use this_cpu_ptr in crypto subsystem cl
2009-06-05 19:18 ` [this_cpu_xx 09/11] X86 optimized this_cpu operations cl
2009-06-05 19:18 ` [this_cpu_xx 10/11] Use this_cpu ops for vm statistics cl
2009-06-05 19:18 ` [this_cpu_xx 11/11] RCU: Use this_cpu operations cl
2009-06-10 17:42 ` 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=20090610174218.GP6773@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=cl@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.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