From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 1/2] memorder: Express `value-returning RMW` more explicitly
Date: Sat, 2 Sep 2017 11:49:36 +0900 [thread overview]
Message-ID: <20170902024937.4227-1-sj38.park@gmail.com> (raw)
A sentence represents `Successful Non-Relaced Non-void RMW' row in
`Linux-Kernel Memory-Ordering Cheat Sheet` as `value-returning RMW` row.
Because it is far different expression, some reader may confuse. This
commit remove the confuse by representing the row with exactly same
words.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
memorder/memorder.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index 3e85eca..5e7176e 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -507,9 +507,9 @@ The \co{*_acquire} row covers \co{smp_load_acquire()},
\co{cmpxchg_acquire()}, \co{xchg_release()}, and so on;
the \co{*_release} row covers \co{smp_store_release()},
\co{cmpxchg_release()}, \co{xchg_release()}, and so on; and
-the value-returning RMW row covers \co{atomic_add_return()},
-\co{atomic_add_unless()},
-\co{atomic_dec_and_test()}, \co{cmpxchg()}, \co{xchg()}, and so on.
+the ``Successful Non-Relaxed Non-\co{void} RMW'' row covers
+\co{atomic_add_return()}, \co{atomic_add_unless()}, \co{atomic_dec_and_test()},
+\co{cmpxchg()}, \co{xchg()}, and so on.
The ``Successful'' qualifiers apply to primitives such as
\co{atomic_add_unless()}, \co{cmpxchg_acquire()}, and \co{cmpxchg_release()},
which have no effect on either memory or on ordering when they indicate
--
2.10.0
next reply other threads:[~2017-09-02 2:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-02 2:49 SeongJae Park [this message]
2017-09-02 2:49 ` [PATCH 2/2] memorder: Add missed closing parenthesis SeongJae Park
2017-09-02 16:12 ` [PATCH 1/2] memorder: Express `value-returning RMW` more explicitly Paul E. McKenney
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=20170902024937.4227-1-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
/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