From: Elad Lahav <e2lahav@gmail.com>
To: perfbook@vger.kernel.org
Cc: Elad Lahav <e2lahav@gmail.com>
Subject: [PATCH] RCU fundamentals: reader is access_route() not read_gptr()
Date: Thu, 17 Nov 2022 02:44:26 -0500 [thread overview]
Message-ID: <20221117074425.157105-1-e2lahav@gmail.com> (raw)
Signed-off-by: Elad Lahav <e2lahav@gmail.com>
---
defer/rcufundamental.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
index 87dfaa95..4abd9d07 100644
--- a/defer/rcufundamental.tex
+++ b/defer/rcufundamental.tex
@@ -56,7 +56,7 @@ It is instead necessary to inform both the compiler and the CPU
of the need for care, as can be seen from
\cref{fig:defer:Publication/Subscription Constraints},
which illustrates interactions between concurrent executions of
-\co{ins_route()} (and its caller) and \co{read_gptr()} from
+\co{ins_route()} (and its caller) and \co{access_route()} from
\cref{lst:defer:Insertion and Deletion With Concurrent Readers}.
The \co{ins_route()} column from
--
2.34.1
next reply other threads:[~2022-11-17 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 7:44 Elad Lahav [this message]
2022-11-17 21:56 ` [PATCH] RCU fundamentals: reader is access_route() not read_gptr() 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=20221117074425.157105-1-e2lahav@gmail.com \
--to=e2lahav@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).