From: Junchang Wang <junchang2020@gmail.com>
To: perfbook@vger.kernel.org
Subject: [PATCH] datastruct.tex: fix some minor typos
Date: Wed, 12 Feb 2020 22:35:15 +0800 [thread overview]
Message-ID: <20200212143457.GA25828@PhD> (raw)
Signed-off-by: Junchang Wang <junchangwang@gmail.com>
---
Hi Paul,
I'm reading the latest version of the perfbook and this patch contains fixes to
some typos in Section Data Structures. Hope it helps.
Thanks,
--Junchang
--
datastruct/datastruct.tex | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/datastruct/datastruct.tex b/datastruct/datastruct.tex
index 4b62471..e21952b 100644
--- a/datastruct/datastruct.tex
+++ b/datastruct/datastruct.tex
@@ -700,7 +700,7 @@ Of course, it is quite possible that the differences in lookup performance
are affected by the differences in update rates.
One way to check this is to artificially throttle the update rates of
per-bucket locking and hazard pointers to match that of RCU.
-Doing so does not significantly improve the lookup performace of
+Doing so does not significantly improve the lookup performance of
per-bucket locking, nor does it close the gap between hazard pointers
and RCU.
However, removing the read-side memory barriers from hazard pointers
@@ -800,8 +800,8 @@ scalability, external consistency, or all of the above.
\section{Non-Partitionable Data Structures}
\label{sec:datastruct:Non-Partitionable Data Structures}
%
-\epigraph{Undertake somthing difficult, otherwise you will never grow.}
- {\emph{Ronald E.~Osburn}}
+\epigraph{Undertake something difficult, otherwise you will never grow.}
+ {\emph{Ronald E.~Osborn}}
\begin{figure}[tb]
\centering
@@ -1063,7 +1063,7 @@ Otherwise, a concurrent resize operation has already distributed this
bucket, so line~\lnref{new_hashtbl} proceeds to the new hash table,
line~\lnref{get_newbkt} selects the bucket corresponding to the key,
and line~\lnref{acq_newbkt} acquires the bucket's lock.
-\Clnref{lsp1b}{lsp1e} store the bucket pointer and
+\Clnrefrange{lsp1b}{lsp1e} store the bucket pointer and
pointer-set index into their respective fields in the
\co{ht_lock_state} structure, which again communicates this information to
\co{hashtab_add()}, \co{hashtab_del()}, and \co{hashtab_unlock_mod()}.
--
2.7.4
next reply other threads:[~2020-02-12 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 14:35 Junchang Wang [this message]
2020-02-13 15:28 ` [PATCH] datastruct.tex: fix some minor typos Akira Yokosawa
2020-02-13 19:19 ` Paul E. McKenney
2020-02-14 0:46 ` Junchang Wang
2020-02-14 0:40 ` Junchang Wang
2020-02-14 9:45 ` 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=20200212143457.GA25828@PhD \
--to=junchang2020@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 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.