From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 1/2] memorder: Fix typos
Date: Sat, 5 Jan 2019 15:28:15 -0800 [thread overview]
Message-ID: <20190105232815.GP4170@linux.ibm.com> (raw)
In-Reply-To: <20190105191957.3050-1-sj38.park@gmail.com>
On Sun, Jan 06, 2019 at 04:19:56AM +0900, SeongJae Park wrote:
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good catches, applied and pushed both, 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 cb4d037..56786fa 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -541,13 +541,13 @@ Blank cells indicate that no ordering is supplied.
> The ``Store'' row also covers the store portion of an atomic RMW operation.
> In addition, the ``Load'' row covers the load
> component of a successful value-returning \co{_relaxed()} RMW atomic
> -operation, although the combined ``\co{_relaxed()} RMW Operations''
> +operation, although the combined ``\co{_relaxed()} RMW operation''
> line provides a convenient combined reference in the value-returning case.
> A CPU executing unsuccessful value-returning atomic RMW operations must
> invalidate the corresponding variable from all other CPUs' caches.
> Therefore, oddly enough, unsuccessful value-returning atomic RMW
> operations have many of the properties of a store, which means that the
> -``\co{_relaxed()} RMW Operations'' line also applies to unsuccessful
> +``\co{_relaxed()} RMW operation'' line also applies to unsuccessful
> value-returning atomic RMW operations.
>
> The \co{*_acquire} row covers \co{smp_load_acquire()},
> --
> 2.10.0
>
prev parent reply other threads:[~2019-01-05 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 19:19 [PATCH 1/2] memorder: Fix typos SeongJae Park
2019-01-05 19:19 ` [PATCH 2/2] debugging: Leave double dashes in description headings SeongJae Park
2019-01-05 23:28 ` Paul E. McKenney [this message]
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=20190105232815.GP4170@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.