From: "Paul E. McKenney" <paulmck@kernel.org>
To: Zqiang <qiang1.zhang@intel.com>
Cc: frederic@kernel.org, quic_neeraju@quicinc.com,
joel@joelfernandes.org, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: Remove duplicate settings for rcu boost kthreads affinity
Date: Fri, 16 Dec 2022 17:09:19 -0800 [thread overview]
Message-ID: <20221217010919.GG4001@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20221215090029.2972236-1-qiang1.zhang@intel.com>
On Thu, Dec 15, 2022 at 05:00:29PM +0800, Zqiang wrote:
> Currently, when CPUs going offline, the rcu boost kthreads CPU
> affinity has been reset in rcutree_offline_cpu(), therefore this
> commit remove duplicate settings in rcutree_dead_cpu().
>
> Signed-off-by: Zqiang <qiang1.zhang@intel.com>
One question...
Given that rcutree_offline_cpu() causes rcu_boost_kthread_setaffinity()
to be invoked with the number of the outgoing CPU, but rcutree_dead_cpu()
instead passes in -1, are these two invocations really redundant?
Thanx, paul
> ---
> kernel/rcu/tree.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 65f3dd2fd3ae..20de83ed0c7e 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -4122,15 +4122,10 @@ static void rcu_cleanup_dead_rnp(struct rcu_node *rnp_leaf)
> */
> int rcutree_dead_cpu(unsigned int cpu)
> {
> - struct rcu_data *rdp = per_cpu_ptr(&rcu_data, cpu);
> - struct rcu_node *rnp = rdp->mynode; /* Outgoing CPU's rdp & rnp. */
> -
> if (!IS_ENABLED(CONFIG_HOTPLUG_CPU))
> return 0;
>
> WRITE_ONCE(rcu_state.n_online_cpus, rcu_state.n_online_cpus - 1);
> - /* Adjust any no-longer-needed kthreads. */
> - rcu_boost_kthread_setaffinity(rnp, -1);
> // Stop-machine done, so allow nohz_full to disable tick.
> tick_dep_clear(TICK_DEP_BIT_RCU);
> return 0;
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-12-17 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 9:00 Zqiang
2022-12-17 1:09 ` Paul E. McKenney [this message]
2022-12-17 2:00 ` Zhang, Qiang1
2022-12-17 13:02 ` Zhang, Qiang1
2022-12-21 19:26 ` Paul E. McKenney
2022-12-22 9:42 ` Zhang, Qiang1
2023-01-12 15:07 ` Frederic Weisbecker
2023-01-12 15:29 ` 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=20221217010919.GG4001@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.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
all inboxes | Powered by JetHome®