public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shan Wei <shanwei88@gmail.com>
To: dipankar@in.ibm.com, paulmck@linux.vnet.ibm.com,
	Kernel-Maillist <linux-kernel@vger.kernel.org>,
	cl@linux-foundation.org
Subject: [PATCH 7/9] rcu:  use this_cpu_ptr per-cpu helper instead of per_cpu_ptr(p, raw_smp_processor_id())
Date: Wed, 31 Oct 2012 19:23:03 +0800	[thread overview]
Message-ID: <50910A17.1090600@gmail.com> (raw)

From: Shan Wei <davidshan@tencent.com>

smp_processor_id is defined as raw_smp_processor_id.
replace per_cpu_ptr(p, raw_smp_processor_id()) is also ok.

Signed-off-by: Shan Wei <davidshan@tencent.com>
---
 kernel/rcutree.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/rcutree.c b/kernel/rcutree.c
index 74df86b..3a21fcf 100644
--- a/kernel/rcutree.c
+++ b/kernel/rcutree.c
@@ -1960,7 +1960,7 @@ static void force_quiescent_state(struct rcu_state *rsp)
 	struct rcu_node *rnp_old = NULL;
 
 	/* Funnel through hierarchy to reduce memory contention. */
-	rnp = per_cpu_ptr(rsp->rda, raw_smp_processor_id())->mynode;
+	rnp = this_cpu_ptr(rsp->rda)->mynode;
 	for (; rnp != NULL; rnp = rnp->parent) {
 		ret = (ACCESS_ONCE(rsp->gp_flags) & RCU_GP_FLAG_FQS) ||
 		      !raw_spin_trylock(&rnp->fqslock);
-- 
1.7.1


             reply	other threads:[~2012-10-31 11:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 11:23 Shan Wei [this message]
2012-10-31 11:51 ` [PATCH 7/9] rcu: use this_cpu_ptr per-cpu helper instead of per_cpu_ptr(p, raw_smp_processor_id()) Paul E. McKenney
2012-10-31 13:20   ` Shan Wei
2012-10-31 13:35     ` Paul E. McKenney
2012-10-31 17:47 ` Christoph Lameter
2012-10-31 20:08   ` Paul E. McKenney
2012-11-01  9:09     ` Shan Wei
2012-11-01 14:32       ` Christoph Lameter

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=50910A17.1090600@gmail.com \
    --to=shanwei88@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.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