From: "Paul E. McKenney" <paulmck@kernel.org>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
rostedt@goodmis.org, ankur.a.arora@oracle.com,
tglx@linutronix.de, mark.rutland@arm.com
Subject: [PATCH rcu 0/4] Refactor TASKS_RCU for lazy preemption
Date: Thu, 22 Feb 2024 16:26:18 -0800 [thread overview]
Message-ID: <8c938bd5-6d62-4eff-9289-13b0d7ae8e17@paulmck-laptop> (raw)
Hello!
This series refactors the NEED_TASKS_RCU option so that the conditional
processing is in one place in kernel/rcu/Kconfig. This makes it easier
to make sure that Tasks RCU is enabled in PREEMPT_AUTO kernels, given
that such kernels are preemptible, even if only lazily so. After all,
it takes only one lazy preemption from a trampoline to significantly
degrade your kernel's actuarial statistics.
1. Create NEED_TASKS_RCU to factor out enablement logic.
2. Select new NEED_TASKS_RCU Kconfig option.
3. Select new NEED_TASKS_RCU Kconfig option.
4. Select new NEED_TASKS_RCU Kconfig option.
Thanx, Paul
------------------------------------------------------------------------
arch/Kconfig | 4 ++--
kernel/bpf/Kconfig | 2 +-
kernel/rcu/Kconfig | 6 +++++-
kernel/trace/Kconfig | 4 ++--
4 files changed, 10 insertions(+), 6 deletions(-)
next reply other threads:[~2024-02-23 0:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 0:26 Paul E. McKenney [this message]
2024-02-23 0:26 ` [PATCH rcu 1/4] rcu: Create NEED_TASKS_RCU to factor out enablement logic Paul E. McKenney
2024-02-23 0:26 ` [PATCH rcu 2/4] bpf: Select new NEED_TASKS_RCU Kconfig option Paul E. McKenney
2024-02-23 0:26 ` [PATCH rcu 3/4] arch: " Paul E. McKenney
2024-02-23 1:36 ` Steven Rostedt
2024-02-23 4:57 ` Paul E. McKenney
2024-02-23 0:26 ` [PATCH rcu 4/4] tracing: " Paul E. McKenney
2024-02-23 10:54 ` [PATCH rcu 0/4] Refactor TASKS_RCU for lazy preemption Mark Rutland
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=8c938bd5-6d62-4eff-9289-13b0d7ae8e17@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=ankur.a.arora@oracle.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).