From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akys@qa2.so-net.ne.jp>
Subject: [PATCH -perfbook 2/2] defer/whichtochoose: Fix trivial typos
Date: Fri, 24 Jun 2022 23:28:16 +0900 [thread overview]
Message-ID: <6329b0e3-2f56-c156-e5e7-883cb381f613@gmail.com> (raw)
In-Reply-To: <6957b314-8f59-9671-4adb-37206fc3c693@qa2.so-net.ne.jp>
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
defer/whichtochoose.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/defer/whichtochoose.tex b/defer/whichtochoose.tex
index 95b355a1c471..489299a7ae02 100644
--- a/defer/whichtochoose.tex
+++ b/defer/whichtochoose.tex
@@ -83,7 +83,7 @@ techniques from one another.
The ``Readers'' row summarizes the results presented in
\cref{fig:defer:Pre-BSD Routing Table Protected by RCU QSBR},
which shows that all but \IXalt{reference counting}{reference count}
-are enjoy reasonably fast and scalable readers.
+enjoy reasonably fast and scalable readers.
The ``Number of Protected Objects'' row evaluates each technique's need
for external storage with which to record reader protection.
@@ -336,7 +336,7 @@ has a \IXalth{bounded wait-free}{bounded}{wait free}
it can carry out a finite traversal by executing a bounded number of
instructions.
-The ``Reader Reference Acquisition'' rows indicates that only RCU is
+The ``Reader Reference Acquisition'' row indicates that only RCU is
capable of unconditionally acquiring references.
The entry for sequence locks is ``Unsafe'' because, again, sequence locks
detect updates rather than acquiring references.
--
2.25.1
prev parent reply other threads:[~2022-06-24 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:26 [PATCH -perfbook 1/2] defer/whichtochoose: Use parnotes for footnote in tabularx Akira Yokosawa
2022-06-24 14:28 ` Akira Yokosawa [this message]
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=6329b0e3-2f56-c156-e5e7-883cb381f613@gmail.com \
--to=akiyks@gmail.com \
--cc=akys@qa2.so-net.ne.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.