From: Thomas Monjalon <thomas@monjalon.net>
To: Tudor Brindus <me@tbrindus.ca>
Cc: dev@dpdk.org
Subject: Re: [PATCH] doc: nohz_full already implies rcu_nocbs
Date: Wed, 16 Mar 2022 20:01:46 +0100 [thread overview]
Message-ID: <3313054.e9J7NaK4W3@thomas> (raw)
In-Reply-To: <20220208035018.795361-1-me@tbrindus.ca>
08/02/2022 04:50, Tudor Brindus:
> From Documentation/admin-guide/kernel-parameters.txt, specifically the
> last sentence:
>
> nohz_full= [KNL,BOOT,SMP,ISOL]
> The argument is a cpu list, as described above.
> In kernels built with CONFIG_NO_HZ_FULL=y, set
> the specified list of CPUs whose tick will be stopped
> whenever possible. The boot CPU will be forced outside
> the range to maintain the timekeeping. Any CPUs
> in this list will have their RCU callbacks offloaded,
> just as if they had also been called out in the
> rcu_nocbs= boot parameter.
>
> The kernel or-s the nohz_full cpumask into the rcu_nocbs cpumask at
> startup, and uses that.
>
> Signed-off-by: Tudor Brindus <me@tbrindus.ca>
Applied, thanks.
prev parent reply other threads:[~2022-03-16 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 3:50 Tudor Brindus
2022-03-16 19:01 ` Thomas Monjalon [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=3313054.e9J7NaK4W3@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=me@tbrindus.ca \
/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;
as well as URLs for NNTP newsgroup(s).