memorder: fix a typo in Listing 15.25's caption
PATCH 1/1 memorder: fix a typo in Listing 15.25's caption
Caption of Listing 15.25 should be "Z6.2 Release-Acquire Chain (Ordering?)" instead of "Z6.0 Release-Acquire Chain (Ordering?)"
---
Hi Paul and Akira:
I guess there is a typo in caption of listing 15.25
Many thanks
Zhouyi
--
memorder/memorder.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
memorder/memorder.tex +4 -4
@@ -2325,14 +2325,14 @@ prevents the \co{exists} clause on \clnref{exists} from triggering. \begin{listing} \input{CodeSamples/formal/litmus/[email protected]} -\caption{Z6.0 Release-Acquire Chain (Ordering?)} -\label{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)} +\caption{Z6.2 Release-Acquire Chain (Ordering?)} +\label{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)} \end{listing} \QuickQuiz{ Suppose we have a short release-acquire chain along with one load-to-store link and one store-to-store link, like that shown in - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}. + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}. Given that there is only one of each type of non-store-to-load link, the \co{exists} cannot trigger, right? }\QuickQuizAnswer{
@@ -2345,7 +2345,7 @@ prevents the \co{exists} clause on \clnref{exists} from triggering. thereof, it is necessary to have at least one full barrier (\co{smp_mb()} or better) between each non-store-to-load link. In - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}, + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}, preventing the \co{exists} clause from triggering therefore requires an additional full barrier between either \co{P0()}'s or \co{P1()}'s accesses.
Signature · 1 line
2.34.1
Hi,
Quoted 8 lines · Zhouyi Zhou
Caption of Listing 15.25 should be "Z6.2 Release-Acquire Chain (Ordering?)" instead of "Z6.0 Release-Acquire Chain (Ordering?)"
Signed-off-by Zhouyi Zhou <[email protected]>---
Hi Paul and Akira:I guess there is a typo in caption of listing 15.25
Nice catch!
Thanks, Akira
Quoted 38 lines
Many thanks
Zhouyi
--memorder/memorder.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)memorder/memorder.tex +4
-4@@ -2325,14 +2325,14 @@ prevents the \co{exists} clause on \clnref{exists} from triggering. \begin{listing} \input{CodeSamples/formal/litmus/[email protected]} -\caption{Z6.0 Release-Acquire Chain (Ordering?)} -\label{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)} +\caption{Z6.2 Release-Acquire Chain (Ordering?)} +\label{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)} \end{listing} \QuickQuiz{ Suppose we have a short release-acquire chain along with one load-to-store link and one store-to-store link, like that shown in - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}. + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}. Given that there is only one of each type of non-store-to-load link, the \co{exists} cannot trigger, right? }\QuickQuizAnswer{@@ -2345,7 +2345,7 @@ prevents the \co{exists} clause on \clnref{exists} from triggering. thereof, it is necessary to have at least one full barrier (\co{smp_mb()} or better) between each non-store-to-load link. In - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}, + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}, preventing the \co{exists} clause from triggering therefore requires an additional full barrier between either \co{P0()}'s or \co{P1()}'s accesses.
Paul E. McKenney
AppliedQuoted 10 lines · Akira Yokosawa
Hi,
Quoted 7 lines · Zhouyi Zhou
Caption of Listing 15.25 should be "Z6.2 Release-Acquire Chain (Ordering?)" instead of "Z6.0 Release-Acquire Chain (Ordering?)"
Signed-off-by Zhouyi Zhou <[email protected]>---
Hi Paul and Akira:
Quoted 5 lines
Quoted 1 line
I guess there is a typo in caption of listing 15.25
Nice catch!
Reviewed-by Akira Yokosawa <[email protected]>
Queued, thank you both!
Thanx, Paul
Quoted 37 lines
Quoted 37 lines
Many thanks
Zhouyi
--memorder/memorder.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)memorder/memorder.tex +4
-4@@ -2325,14 +2325,14 @@ prevents the \co{exists} clause on \clnref{exists} from triggering. \begin{listing} \input{CodeSamples/formal/litmus/[email protected]} -\caption{Z6.0 Release-Acquire Chain (Ordering?)} -\label{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)} +\caption{Z6.2 Release-Acquire Chain (Ordering?)} +\label{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)} \end{listing} \QuickQuiz{ Suppose we have a short release-acquire chain along with one load-to-store link and one store-to-store link, like that shown in - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}. + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}. Given that there is only one of each type of non-store-to-load link, the \co{exists} cannot trigger, right? }\QuickQuizAnswer{@@ -2345,7 +2345,7 @@ prevents the \co{exists} clause on \clnref{exists} from triggering. thereof, it is necessary to have at least one full barrier (\co{smp_mb()} or better) between each non-store-to-load link. In - \cref{lst:memorder:Z6.0 Release-Acquire Chain (Ordering?)}, + \cref{lst:memorder:Z6.2 Release-Acquire Chain (Ordering?)}, preventing the \co{exists} clause from triggering therefore requires an additional full barrier between either \co{P0()}'s or \co{P1()}'s accesses.