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, "Paul E. McKenney" <paulmck@kernel.org>
Subject: [PATCH rcu v2 6/7] rcu: Clarify RCU_LAZY and RCU_LAZY_DEFAULT_OFF help text
Date: Thu, 30 Jan 2025 10:49:24 -0800 [thread overview]
Message-ID: <20250130184925.1651665-6-paulmck@kernel.org> (raw)
In-Reply-To: <851fd11f-6397-4411-983b-96f7234326d5@paulmck-laptop>
This commit wordsmiths the RCU_LAZY and RCU_LAZY_DEFAULT_OFF Kconfig
options' help text.
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
kernel/rcu/Kconfig | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/kernel/rcu/Kconfig b/kernel/rcu/Kconfig
index b9b6bc55185d..2bb22dac3b5a 100644
--- a/kernel/rcu/Kconfig
+++ b/kernel/rcu/Kconfig
@@ -323,21 +323,27 @@ config RCU_LAZY
depends on RCU_NOCB_CPU
default n
help
- To save power, batch RCU callbacks and flush after delay, memory
- pressure, or callback list growing too big.
+ To save power, batch RCU callbacks and delay starting the
+ corresponding grace period for multiple seconds. The grace
+ period will be started after this delay, in case of memory
+ pressure, or if the corresponding CPU's callback list grows
+ too large.
- Requires rcu_nocbs=all to be set.
+ These delays happen only on rcu_nocbs CPUs, that is, CPUs
+ whose callbacks have been offloaded.
- Use rcutree.enable_rcu_lazy=0 to turn it off at boot time.
+ Use the rcutree.enable_rcu_lazy=0 kernel-boot parameter to
+ globally disable these delays.
config RCU_LAZY_DEFAULT_OFF
bool "Turn RCU lazy invocation off by default"
depends on RCU_LAZY
default n
help
- Allows building the kernel with CONFIG_RCU_LAZY=y yet keep it default
- off. Boot time param rcutree.enable_rcu_lazy=1 can be used to switch
- it back on.
+ Build the kernel with CONFIG_RCU_LAZY=y, but cause the kernel
+ to boot with these energy-efficiency delays disabled. Use the
+ rcutree.enable_rcu_lazy=0 kernel-boot parameter to override
+ the this option at boot time, thus re-enabling these delays.
config RCU_DOUBLE_CHECK_CB_TIME
bool "RCU callback-batch backup time check"
--
2.40.1
next prev parent reply other threads:[~2025-01-30 18:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 20:02 [PATCH rcu 0/7] Documentation upates Paul E. McKenney
2025-01-16 20:02 ` [PATCH rcu 1/7] doc: Add broken-timing possibility to stallwarn.rst Paul E. McKenney
2025-01-16 20:02 ` [PATCH rcu 2/7] docs: Improve discussion of this_cpu_ptr(), add raw_cpu_ptr() Paul E. McKenney
2025-01-16 21:02 ` Matthew Wilcox
2025-01-16 22:57 ` Paul E. McKenney
2025-01-16 20:02 ` [PATCH rcu 3/7] rcu: Document self-propagating callbacks Paul E. McKenney
2025-01-16 21:38 ` Jens Axboe
2025-01-16 20:02 ` [PATCH rcu 4/7] srcu: Point call_srcu() to call_rcu() for detailed memory ordering Paul E. McKenney
2025-01-16 20:02 ` [PATCH rcu 5/7] rcu: Add CONFIG_RCU_LAZY delays to call_rcu() kernel-doc header Paul E. McKenney
2025-01-16 20:02 ` [PATCH rcu 6/7] rcu: Clarify RCU_LAZY and RCU_LAZY_DEFAULT_OFF help text Paul E. McKenney
2025-01-16 20:02 ` [PATCH rcu 7/7] rcu: Remove references to old grace-period-wait primitives Paul E. McKenney
2025-01-30 18:47 ` [PATCH rcu 0/7] Documentation upates Paul E. McKenney
2025-01-30 18:49 ` [PATCH rcu v2 1/7] doc: Add broken-timing possibility to stallwarn.rst Paul E. McKenney
2025-01-30 18:49 ` [PATCH rcu v2 2/7] docs: Improve discussion of this_cpu_ptr(), add raw_cpu_ptr() Paul E. McKenney
2025-01-30 18:49 ` [PATCH rcu v2 3/7] rcu: Document self-propagating callbacks Paul E. McKenney
2025-01-30 18:49 ` [PATCH rcu v2 4/7] srcu: Point call_srcu() to call_rcu() for detailed memory ordering Paul E. McKenney
2025-01-30 18:49 ` [PATCH rcu v2 5/7] rcu: Add CONFIG_RCU_LAZY delays to call_rcu() kernel-doc header Paul E. McKenney
2025-01-30 18:49 ` Paul E. McKenney [this message]
2025-01-30 18:49 ` [PATCH rcu v2 7/7] rcu: Remove references to old grace-period-wait primitives 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=20250130184925.1651665-6-paulmck@kernel.org \
--to=paulmck@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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