On Sat, Apr 02, 2016 at 09:28:30AM +0900, SeongJae Park wrote:
> A sentence in `Locking Examples` section says both LOCK and UNLOCK
> allows preceding operations `bleed in` to the critical section.
> However, it's wrong description. LOCK allows only preceding operations
> and UNLOCK allows only following operations to bleed in. Looks like the
> wrong description made by just a trivial mistake. This commit fixes the
> sentence to have correct description.
>
> Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
Queued, thank you!
Thanx, Paul
> ---
> advsync/memorybarriers.tex | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
> index b1f49d3..1fe0953 100644
> --- a/advsync/memorybarriers.tex
> +++ b/advsync/memorybarriers.tex
> @@ -2232,8 +2232,9 @@ might well execute in the following order:
> \end{minipage}
> \vspace{5pt}
>
> -Again, always remember that both LOCK and UNLOCK are permitted to let
> -preceding operations ``bleed in'' to the critical section.
> +Again, always remember that LOCK and UNLOCK are permitted to let preceding
> +operations and following operations ``bleed in'' to the critical section
> +respectively.
>
> \QuickQuiz{}
> What sequence of LOCK-UNLOCK operations \emph{would}
> --
> 1.9.1
>
--
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
