From: "Paul E. McKenney" <paulmck@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] rcu: Eliminate rcu_state.nocb_is_setup
Date: Mon, 22 Aug 2022 09:34:11 -0700 [thread overview]
Message-ID: <20220822163411.GF6159@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220817014253.1982-2-thunder.leizhen@huawei.com>
On Wed, Aug 17, 2022 at 09:42:52AM +0800, Zhen Lei wrote:
> 'rcu_state.nocb_is_setup' is initialized to true only if 'rcu_nocb_mask'
> successfully allocates memory. So it can be replaced by
> 'cpumask_available(rcu_nocb_mask)'. More importantly, the latter is more
> intuitive, and it has been used in several places.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
One of the implementations of cpumask_available() does indeed check
for NULL. But here is the other one:
static inline bool cpumask_available(cpumask_var_t mask)
{
return true;
}
So I have to ask... In a kernel built with CONFIG_CPUMASK_OFFSTACK=n,
will this change really work?
Another important question is "Do all of the existing uses of
cpumask_available() really work?" Yes, I do believe that they do
work, but it would be good to get another set of eyes on that code.
"All software developers are blind!" ;-)
Thanx, Paul
> ---
> kernel/rcu/tree.h | 1 -
> kernel/rcu/tree_nocb.h | 8 +++-----
> 2 files changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/rcu/tree.h b/kernel/rcu/tree.h
> index d4a97e40ea9c3e2..06f659c63d2d192 100644
> --- a/kernel/rcu/tree.h
> +++ b/kernel/rcu/tree.h
> @@ -375,7 +375,6 @@ struct rcu_state {
> arch_spinlock_t ofl_lock ____cacheline_internodealigned_in_smp;
> /* Synchronize offline with */
> /* GP pre-initialization. */
> - int nocb_is_setup; /* nocb is setup from boot */
> };
>
> /* Values for rcu_state structure's gp_flags field. */
> diff --git a/kernel/rcu/tree_nocb.h b/kernel/rcu/tree_nocb.h
> index 0a5f0ef41484518..ff763e7dc53551f 100644
> --- a/kernel/rcu/tree_nocb.h
> +++ b/kernel/rcu/tree_nocb.h
> @@ -69,7 +69,6 @@ static int __init rcu_nocb_setup(char *str)
> cpumask_setall(rcu_nocb_mask);
> }
> }
> - rcu_state.nocb_is_setup = true;
> return 1;
> }
> __setup("rcu_nocbs", rcu_nocb_setup);
> @@ -1215,7 +1214,7 @@ void __init rcu_init_nohz(void)
> struct rcu_data *rdp;
>
> #if defined(CONFIG_RCU_NOCB_CPU_DEFAULT_ALL)
> - if (!rcu_state.nocb_is_setup) {
> + if (!cpumask_available(rcu_nocb_mask)) {
> need_rcu_nocb_mask = true;
> offload_all = true;
> }
> @@ -1235,10 +1234,9 @@ void __init rcu_init_nohz(void)
> return;
> }
> }
> - rcu_state.nocb_is_setup = true;
> }
>
> - if (!rcu_state.nocb_is_setup)
> + if (!cpumask_available(rcu_nocb_mask))
> return;
>
> #if defined(CONFIG_NO_HZ_FULL)
> @@ -1299,7 +1297,7 @@ static void rcu_spawn_cpu_nocb_kthread(int cpu)
> struct task_struct *t;
> struct sched_param sp;
>
> - if (!rcu_scheduler_fully_active || !rcu_state.nocb_is_setup)
> + if (!rcu_scheduler_fully_active || !cpumask_available(rcu_nocb_mask))
> return;
>
> /* If there already is an rcuo kthread, then nothing to do. */
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-08-22 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 1:42 [PATCH v4 0/2] rcu/nocb: Delete local variable 'need_rcu_nocb_mask' in rcu_init_nohz() Zhen Lei
2022-08-17 1:42 ` [PATCH v4 1/2] rcu: Eliminate rcu_state.nocb_is_setup Zhen Lei
2022-08-22 16:34 ` Paul E. McKenney [this message]
2022-08-23 12:00 ` Leizhen (ThunderTown)
2022-08-17 1:42 ` [PATCH v4 2/2] rcu: Simplify the code logic of rcu_init_nohz() Zhen Lei
2022-08-22 16:35 ` Paul E. McKenney
2022-08-23 12:13 ` Leizhen (ThunderTown)
2022-08-25 16:19 ` Paul E. McKenney
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=20220822163411.GF6159@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=thunder.leizhen@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
all inboxes | Powered by JetHome®