>From f0494167b80f2c2760628e34f592982325f41c26 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Wed, 13 Sep 2017 23:56:41 +0900
Subject: [PATCH] memorder: Fix trivial typo
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
memorder/memorder.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index ac03c23..28b9a37 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -2021,7 +2021,7 @@ P2's cache.
Row~2 shows the immediate effect of \co{P0()} executing its store on line~13.
Because the cacheline containing \co{x} is not in \co{P0()}'s and \co{P1()}'s
-shared cache, the new value (\co{&x})is stored in the shared store buffer.
+shared cache, the new value (\co{&x}) is stored in the shared store buffer.
Row~3 shows two transitions.
First, \co{P0()} issues a read-invalidate operation to fetch the cacheline
@@ -2335,7 +2335,7 @@ returned the value stored by the \co{smp_store_release()} on line~12,
the \co{1:r2=0} indicates that the \co{WRITE_ONCE()} on line~28 came
too late to affect the value returned by the \co{READ_ONCE()} on line~21,
and finally the \co{2:r3=0} indicates that the
-\co{WRITE_ONCE()} on line~11 came to late to affect the value returned
+\co{WRITE_ONCE()} on line~11 came too late to affect the value returned
by the \co{READ_ONCE()} on line~30.
In this case, the fact that the \co{exists} clause can trigger means that
the cycle is said to be \emph{allowed}.
@@ -2631,7 +2631,7 @@ but these chains can be much longer, as shown in
Listing~\ref{lst:memorder:Long LB Release-Acquire Chain}.
The longer the release-acquire chain, the more benefit is gained
from the passage of time, so that no matter how many threads are
-involved, the corresponding \co{exists} clause cannot trigger..
+involved, the corresponding \co{exists} clause cannot trigger.
Give or take the increased computational demands of the larger number
of threads, of course!
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
