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/seqlock: Fix read-side smp_mb wording
Date: Tue, 24 Feb 2026 18:35:39 +0800 [thread overview]
Message-ID: <20260224103539.2615348-1-kunwu.chan@linux.dev> (raw)
Signed-off-by: Kunwu Chan <kunwu.chan@linux.dev>
---
defer/seqlock.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/defer/seqlock.tex b/defer/seqlock.tex
index 3ed2f483..6d1d5b78 100644
--- a/defer/seqlock.tex
+++ b/defer/seqlock.tex
@@ -166,7 +166,7 @@ will pass to a later call to \co{read_seqretry()}.
on the update side.
This feature is on its way into the C++ standard under the name
of ``asymmetric fences''~\cite{DavidGoldblatt2022asymmetricFences}.
- Either way, this trick eliminates the update-side \co{smp_mb()}
+ Either way, this trick eliminates the read-side \co{smp_mb()}
overhead, which in turn makes eliminating the check more
attractive, arriving again at the form of the code shown in
\cref{lst:defer:Sequence-Locked Pre-BSD Routing Table Lookup}.
--
2.25.1
reply other threads:[~2026-02-24 10:36 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=20260224103539.2615348-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