From: "Paul E. McKenney" <paulmck@kernel.org>
To: Alison Chaiken <achaiken@aurora.tech>
Cc: tglx@linutronix.de, peterz@infradead.org,
valentin.schneider@arm.com, frederic@kernel.org,
linux-kernel@vger.kernel.org, glenn@aurora.tech,
alison@she-devel.com
Subject: Re: [PATCH 0/5] handle kthread_prio kernel cmdline parameter consistently
Date: Tue, 11 Jan 2022 17:03:02 -0800 [thread overview]
Message-ID: <20220112010302.GL947480@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <20220111233253.21692-1-achaiken@aurora.tech>
On Tue, Jan 11, 2022 at 03:32:49PM -0800, Alison Chaiken wrote:
> When CONFIG_PREEMPT_RT=y, RCU_SOFTIRQ work is moved to dedicated rcuc
> per-core threads. The rcutree.kthread_prio kernel cmdline parameter
> controls the priority of those threads.
>
> A provided kthread_prio kernel cmdline parameter also elevates the
> priority of rcuog threads, but only if they are launched from
> rcu_spawn_gp_kthread(), not if they are launched from
> rcu_spawn_one_nocb_kthread(). Fix this inconsistency.
>
> When CONFIG_RCU_NOCB_CPU=y, an rcu_nocbs command-line parameter
> offloads the work of rcuc on designated cores to new rcuop threads
> that are not pinned to the cores whose expired grace-period timer
> callbacks they run. While rcuop threads have the same function as
> rcuc threads, their priority is not controlled by the kthread_prio
> parameter. Add this feature and update the documentation accordingly.
>
> Alison Chaiken (4):
> RCU: move kthread_prio bounds-check to a separate function
> RCU: make priority of grace-period thread consistent
> RCU: elevate priority of offloaded callback threads
> RCU: update documentation regarding kthread_prio cmdline parameter
I have queued these for review and testing, thank you!
2/4 appears to have been produced against a pre-merge-window mainline,
so I had to adjust it a bit to queue it on -rcu. Please check to make
sure that I did not mess anything up.
Thanx, Paul
prev parent reply other threads:[~2022-01-12 1:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 23:32 Alison Chaiken
2022-01-11 23:32 ` [PATCH 1/4] RCU: move kthread_prio bounds-check to a separate function Alison Chaiken
2022-01-11 23:32 ` [PATCH 2/4] RCU: make priority of grace-period thread consistent Alison Chaiken
2022-01-11 23:32 ` [PATCH 3/4] RCU: elevate priority of offloaded callback threads Alison Chaiken
2022-01-11 23:32 ` [PATCH 4/4] RCU: update documentation regarding kthread_prio cmdline parameter Alison Chaiken
2022-01-12 1:03 ` Paul E. McKenney [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=20220112010302.GL947480@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=achaiken@aurora.tech \
--cc=alison@she-devel.com \
--cc=frederic@kernel.org \
--cc=glenn@aurora.tech \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.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®