Re: [PATCH -perfbook] memorder: fix a typo in Listing 15.25's caption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Wed, 19 Oct 2022 16:44:42 +0800, Zhouyi Zhou wrote:
> 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 <zhouzhouyi@xxxxxxxxx>
> ---
> Hi Paul and Akira:
> 
> I guess there is a typo in caption of listing 15.25

Nice catch!

Reviewed-by: Akira Yokosawa <akiyks@xxxxxxxxx>

        Thanks, Akira
> 
> Many thanks
> Zhouyi
> --
>  memorder/memorder.tex | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> index 28319bfb..0c96d43b 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -2325,14 +2325,14 @@ prevents the \co{exists} clause on \clnref{exists} from triggering.
>  
>  \begin{listing}
>  \input{CodeSamples/formal/litmus/C-Z6.2+o-r+a-o+o-mb-o@xxxxxxxxx}
> -\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.



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux