From: Mark Rutland <mark.rutland@arm.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com, rostedt@goodmis.org,
ankur.a.arora@oracle.com, tglx@linutronix.de
Subject: Re: [PATCH rcu 0/4] Refactor TASKS_RCU for lazy preemption
Date: Fri, 23 Feb 2024 10:54:28 +0000 [thread overview]
Message-ID: <Zdh5ZIboTTQJjG1i@FVFF77S0Q05N> (raw)
In-Reply-To: <8c938bd5-6d62-4eff-9289-13b0d7ae8e17@paulmck-laptop>
On Thu, Feb 22, 2024 at 04:26:18PM -0800, Paul E. McKenney wrote:
> Hello!
Hi!
> 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.
For the series:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
prev parent reply other threads:[~2024-02-23 10:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 0:26 [PATCH rcu 0/4] Refactor TASKS_RCU for lazy preemption Paul E. McKenney
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 ` Mark Rutland [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=Zdh5ZIboTTQJjG1i@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=ankur.a.arora@oracle.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--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).