From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Yao Dongdong <yaodongdong@huawei.com>
Cc: josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, laijs@cn.fujitsu.com,
linux-kernel@vger.kernel.org, lizefan@huawei.com
Subject: Re: [PATCH] rcu: Remove reduplicate check of cpu_online
Date: Wed, 25 Feb 2015 11:00:28 -0800 [thread overview]
Message-ID: <20150225190028.GP15405@linux.vnet.ibm.com> (raw)
In-Reply-To: <1424855386-8280-1-git-send-email-yaodongdong@huawei.com>
On Wed, Feb 25, 2015 at 05:09:46PM +0800, Yao Dongdong wrote:
> The calling function invoke_rcu_core will check it.
>
> Signed-off-by: Yao Dongdong <yaodongdong@huawei.com>
Hmmm... That is a fastpath, but invoke_rcu_core() is visible to the compiler,
which should inline anyway. I took this patch for 4.1, but updated
the title and commit log as follows:
rcu: Remove redundant check of cpu_online()
Because invoke_cpu_core() checks whether the current CPU is online,
there is no need for __call_rcu_core() to redundantly check it.
There should not be any performance degradation because the called
function is visible to the compiler. This commit therefore removes
the redundant check.
Thanx, Paul
> ---
> kernel/rcu/tree.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 48d640c..e5f9b7e 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -2741,7 +2741,7 @@ static void __call_rcu_core(struct rcu_state *rsp, struct rcu_data *rdp,
> * If called from an extended quiescent state, invoke the RCU
> * core in order to force a re-evaluation of RCU's idleness.
> */
> - if (!rcu_is_watching() && cpu_online(smp_processor_id()))
> + if (!rcu_is_watching())
> invoke_rcu_core();
>
> /* If interrupts were disabled or CPU offline, don't invoke RCU core. */
> --
> 1.7.9.5
>
prev parent reply other threads:[~2015-02-25 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 9:09 [PATCH] rcu: Remove reduplicate check of cpu_online Yao Dongdong
2015-02-25 19:00 ` 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=20150225190028.GP15405@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=yaodongdong@huawei.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