Linux RCU subsystem development
 help / color / mirror / Atom feed
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 4/7] srcu: Point call_srcu() to call_rcu() for detailed memory ordering
Date: Thu, 16 Jan 2025 12:02:36 -0800	[thread overview]
Message-ID: <20250116200239.3782374-4-paulmck@kernel.org> (raw)
In-Reply-To: <a2c2793d-771a-436e-8c42-4cb38def0e2f@paulmck-laptop>

This commit causes the call_srcu() kernel-doc header to reference that
of call_rcu() for detailed memory-ordering guarantees.

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
 kernel/rcu/srcutree.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
index b83c74c4dcc0d..f87a9fb6d6bb8 100644
--- a/kernel/rcu/srcutree.c
+++ b/kernel/rcu/srcutree.c
@@ -1398,8 +1398,12 @@ static void __call_srcu(struct srcu_struct *ssp, struct rcu_head *rhp,
  * read-side critical sections are delimited by srcu_read_lock() and
  * srcu_read_unlock(), and may be nested.
  *
- * The callback will be invoked from process context, but must nevertheless
- * be fast and must not block.
+ * The callback will be invoked from process context, but with bh
+ * disabled.  The callback function must therefore be fast and must
+ * not block.
+ *
+ * See the description of call_rcu() for more detailed information on
+ * memory ordering guarantees.
  */
 void call_srcu(struct srcu_struct *ssp, struct rcu_head *rhp,
 	       rcu_callback_t func)
-- 
2.40.1


  parent reply	other threads:[~2025-01-16 20:02 UTC|newest]

Thread overview: 20+ 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 ` Paul E. McKenney [this message]
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   ` [PATCH rcu v2 6/7] rcu: Clarify RCU_LAZY and RCU_LAZY_DEFAULT_OFF help text Paul E. McKenney
2025-01-30 18:49   ` [PATCH rcu v2 7/7] rcu: Remove references to old grace-period-wait primitives Paul E. McKenney
  -- strict thread matches above, loose matches on Subject: below --
2025-02-18  5:45 [PATCH rcu 0/7] RCU documentation changes for v6.15 Boqun Feng
2025-02-18  5:45 ` [PATCH rcu 4/7] srcu: Point call_srcu() to call_rcu() for detailed memory ordering Boqun Feng

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=20250116200239.3782374-4-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