From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, rostedt@goodmis.org,
Zhen Lei <thunder.leizhen@huawei.com>,
Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [PATCH rcu 3/3] rcu: Simplify rcu_init_nohz() cpumask handling
Date: Thu, 1 Sep 2022 13:11:14 +0200 [thread overview]
Message-ID: <20220901111114.GA103483@lothringen> (raw)
In-Reply-To: <20220901102520.GQ6159@paulmck-ThinkPad-P17-Gen-1>
On Thu, Sep 01, 2022 at 03:25:20AM -0700, Paul E. McKenney wrote:
> On Thu, Sep 01, 2022 at 11:15:57AM +0200, Frederic Weisbecker wrote:
> > > +#elif defined(CONFIG_NO_HZ_FULL)
> > > + if (tick_nohz_full_running && !cpumask_empty(tick_nohz_full_mask))
> > > + cpumask = tick_nohz_full_mask;
> > > +#endif
> >
> > A subtle behaviour difference here too: CONFIG_RCU_NOCB_CPU_DEFAULT_ALL will
> > now override nohz_full=
> >
> > I don't mind, it's probably what we want in the end, but the changelog should
> > tell about it, or even better, this should be a separate change.
>
> Good point. Perhaps the key point is that if there is nohz_full=,
> rcu_nocbs=, and CONFIG_RCU_NOCB_CPU_DEFAULT_ALL, we still need rcu_nocbs=
> to include at least those bits set by nohz_full=.
Not sure I get what you mean. nohz_full= should in any case always force
rcu_nocbs at least on the nohz_full CPUs.
For example assuming the following combination: rcu_nocbs=6, nohz_full=7 AND
CONFIG_RCU_NOCB_CPU_DEFAULT_ALL=y, then the result should be:
NOCB CPUs = 6,7
NOHZ_FULL CPUs = 7
(CONFIG_RCU_NOCB_CPU_DEFAULT_ALL=y is overriden by rcu_nocbs=6).
Now if we have nohz_full=7 AND CONFIG_RCU_NOCB_CPU_DEFAULT_ALL=y, then the
result is expected to be either:
NOCB CPUs = 7 (upstream behaviour)
NOHZ_FULL CPUs = 7
or
NOCB CPUs = all
NOHZ_FULL CPUs = 7
The second makes more sense IMHO but that should be in a separate change.
Thanks.
next prev parent reply other threads:[~2022-09-01 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 18:10 [PATCH rcu 0/7] Callback-offload (nocb) updates for v6.1 Paul E. McKenney
2022-08-31 18:10 ` [PATCH rcu 1/3] rcu/nocb: Choose the right rcuog/rcuop kthreads to output Paul E. McKenney
2022-08-31 18:10 ` [PATCH rcu 2/3] rcu/nocb: Add CPU number to CPU-{,de}offload failure messages Paul E. McKenney
2022-08-31 18:10 ` [PATCH rcu 3/3] rcu: Simplify rcu_init_nohz() cpumask handling Paul E. McKenney
2022-09-01 9:15 ` Frederic Weisbecker
2022-09-01 10:25 ` Paul E. McKenney
2022-09-01 11:11 ` Frederic Weisbecker [this message]
2022-09-01 11:36 ` Leizhen (ThunderTown)
2022-09-01 13:31 ` 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=20220901111114.GA103483@lothringen \
--to=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.