public inbox for perfbook@vger.kernel.org
 help / color / mirror / Atom feed
From: Kunwu Chan <kunwu.chan@linux.dev>
To: perfbook@vger.kernel.org
Cc: paulmck@kernel.org, Kunwu Chan <kunwu.chan@linux.dev>
Subject: [PATCH] defer/rcufundamental: Clarify rcu_dereference() ordering semantics
Date: Wed, 25 Feb 2026 19:01:26 +0800	[thread overview]
Message-ID: <20260225110126.3266260-1-kunwu.chan@linux.dev> (raw)

Replace a grammar-only sentence with wording aligned with the
normative statement in defer/rcuintro.tex. That statement defines
rcu_dereference() as preventing compiler and (in one case) CPU
reordering of the pointer load with later dereference-side memory
operations.

Signed-off-by: Kunwu Chan <kunwu.chan@linux.dev>
---
 defer/rcufundamental.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
index c3bcc4f0..ccfe9133 100644
--- a/defer/rcufundamental.tex
+++ b/defer/rcufundamental.tex
@@ -118,9 +118,9 @@ synchronization overhead.
 	before freeing the removed data.
 }\QuickQuizEnd
 
-Subscription is carried out by \co{rcu_dereference()}, which orders
-the subscription operation's load from the pointer is before the
-dereference.
+Subscription is carried out by \co{rcu_dereference()}, which prevents
+the compiler and (in one case) the CPU from reordering the pointer
+load with later memory operations that dereference that pointer.
 Similar to \co{rcu_assign_pointer()}, \co{rcu_dereference()} must be
 atomic in the sense that the value loaded must be that from a single
 store, for example, the compiler must not tear the load.\footnote{
-- 
2.25.1


                 reply	other threads:[~2026-02-25 11:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260225110126.3266260-1-kunwu.chan@linux.dev \
    --to=kunwu.chan@linux.dev \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.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