All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junchang Wang <junchangwang@gmail.com>
To: paulmck@linux.vnet.ibm.com, akiyks@gmail.com
Cc: perfbook@vger.kernel.org, Junchang Wang <junchangwang@gmail.com>
Subject: [PATCH] memorder: Add a brief description of the use of multicopy atomicity
Date: Thu,  8 Nov 2018 10:21:31 +0800	[thread overview]
Message-ID: <1541643691-8116-1-git-send-email-junchangwang@gmail.com> (raw)

Subsection Multicopy Atomicity is ahead of Subsection Hardware Specifics where
implementation detail of multicopy atomicity in mainstream architectures is
presented. So we add (1) a brief description of the use of multicopy atomicity
in representative architectures and (2) a reference to Table Summary of Memory
Ordering, in subsection Multicopy Atomicity.

The description is borrowed from a nice discussion with Paul, which can be found
at https://www.spinics.net/lists/perfbook/msg01952.html.

Signed-off-by: Junchang Wang <junchangwang@gmail.com>
---
 memorder/memorder.tex | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index fba49b7..69ce196 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -1901,7 +1901,11 @@ Most CPU vendors interested in providing multicopy atomicity have therefore
 instead provided the slightly weaker
 \emph{other-multicopy atomicity}~\cite[Section B2.3]{ARMv8A:2017},
 which excludes the CPU doing a given store from the requirement that all
-CPUs agree on the order of all stores.
+CPUs agree on the order of all stores.\footnote{
+	As of late 2018, ARMv8 and x86 provide other-multicopy atomicity,
+	IBM mainframe provides fully multicopy atomicity, and PPC does
+	not provide multicopy atomicity at all. More detail is shown in
+	Figure~\ref{tab:memorder:Summary of Memory Ordering}.}
 This means that if only a subset of CPUs are doing stores, the
 other CPUs will agree on the order of stores, hence the ``other''
 in ``other-multicopy atomicity''.
-- 
2.7.4


             reply	other threads:[~2018-11-08  2:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08  2:21 Junchang Wang [this message]
2018-11-08  6:34 ` [PATCH] memorder: Add a brief description of the use of multicopy atomicity 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=1541643691-8116-1-git-send-email-junchangwang@gmail.com \
    --to=junchangwang@gmail.com \
    --cc=akiyks@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 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.