Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] memorder: Fix two trivial typos
Date: Tue, 2 Apr 2019 06:32:22 -0700	[thread overview]
Message-ID: <20190402133222.GY4102@linux.ibm.com> (raw)
In-Reply-To: <20190402001457.31848-1-sj38.park@gmail.com>

On Tue, Apr 02, 2019 at 09:14:57AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Good catch, queued and pushed, thank you!

							Thanx, Paul

> ---
>  memorder/memorder.tex | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> index 1649ce9..bb380ad 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -3125,7 +3125,7 @@ Sections~\ref{sec:toolsoftrade:A Volatile Solution}-\ref{sec:toolsoftrade:Avoidi
>  	cause the compiler to discard a previously loaded value from
>  	its register, and then reload it later on.
>  	Invented loads can be prevented by using \co{READ_ONCE()} or by
> -	enforcing ordering as callout out above between the load and a
> +	enforcing ordering as called out above between the load and a
>  	later use of its value using \co{barrier()}.
>  \item	Stores can be invented before a plain store, for example, by
>  	using the stored-to location as temporary storage.
> @@ -3160,7 +3160,7 @@ optimizing your parallel algorithm out of existence.
>  Compilers are starting to provide other mechanisms for avoiding
>  load and store tearing, for example, \co{memory_order_relaxed}
>  atomic loads and stores, however, work is still
> -needed~/\cite{JonathanCorbet2016C11atomics}
> +needed~\cite{JonathanCorbet2016C11atomics}.
>  In addition, compiler issues aside, \co{volatile} is still needed
>  to avoid fusing and invention of accesses, including C11 atomic accesses.
>  
> -- 
> 2.10.0
> 


  reply	other threads:[~2019-04-02 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  0:14 [PATCH] memorder: Fix two trivial typos SeongJae Park
2019-04-02 13:32 ` Paul E. McKenney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-26  0:56 SeongJae Park

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=20190402133222.GY4102@linux.ibm.com \
    --to=paulmck@linux.ibm.com \
    --cc=perfbook@vger.kernel.org \
    --cc=sj38.park@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox