From: "Paul E. McKenney" <paulmck@kernel.org>
To: Zqiang <qiang1.zhang@intel.com>
Cc: frederic@kernel.org, linux-kernel@vger.kernel.org, bigeasy@linutronix.de
Subject: Re: [PATCH] rcu: per-cpu rcuc kthread are created only when rcutree.use_softirq=0
Date: Sat, 1 Jan 2022 08:44:26 -0800 [thread overview]
Message-ID: <20220101164426.GA2408833@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20211228160510.2893362-1-qiang1.zhang@intel.com>
On Wed, Dec 29, 2021 at 12:05:10AM +0800, Zqiang wrote:
> In non-RT kernel, if the RCU_BOOST is enabled, the per-cpu rcuc
> kthread will be created, however under the rcutree.use_softirq=1,
> the RCU core processing only in softirq context, the rcuc kthread
> doesn't do anything, so remove RCU_BOOST interference.
>
> Signed-off-by: Zqiang <qiang1.zhang@intel.com>
Looks sane to me, but adding Sebastian on CC for his thoughts.
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 9b58bae0527a..ed64b4fcb8a0 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -2902,7 +2902,7 @@ static int __init rcu_spawn_core_kthreads(void)
>
> for_each_possible_cpu(cpu)
> per_cpu(rcu_data.rcu_cpu_has_work, cpu) = 0;
> - if (!IS_ENABLED(CONFIG_RCU_BOOST) && use_softirq)
> + if (use_softirq)
> return 0;
> WARN_ONCE(smpboot_register_percpu_thread(&rcu_cpu_thread_spec),
> "%s: Could not start rcuc kthread, OOM is now expected behavior\n", __func__);
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-01-01 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-28 16:05 Zqiang
2022-01-01 16:44 ` Paul E. McKenney [this message]
2022-01-03 13:17 ` Sebastian Andrzej Siewior
2022-01-03 14:34 ` Paul E. McKenney
2022-01-04 8:38 ` Zhang, Qiang1
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=20220101164426.GA2408833@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang1.zhang@intel.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®