Other-multicopy atomicity
Hi Paul,
I have a comment on the term "other-multicompy atomicity".
It took a while for me to realize that the "other-" stands for "other than self CPU". At first, it sounded like "other type of multicompy atomicity", which looked quite vague.
Commit 43236beadb1 ("memorder: Expand on cumulativity and {other,} multicopy atomicity") helped me to realize your intention. May I suggest to add a footnote on the use of "other-"?
Also, you failed to replace tabs to white spaces in listing added in the above mentioned commit.
Thanks, Akira
Quoted 11 lines · Akira Yokosawa
Hi Paul,
I have a comment on the term "other-multicompy atomicity".
It took a while for me to realize that the "other-" stands for "other than self CPU". At first, it sounded like "other type of multicompy atomicity", which looked quite vague.
Commit
43236beadb1("memorder: Expand on cumulativity and {other,} multicopy atomicity") helped me to realize your intention. May I suggest to add a footnote on the use of "other-"?
I am trying to do a bit too much with that paragraph, aren't I?
How about the patch below?
Quoted 2 lines
Also, you failed to replace tabs to white spaces in listing added in the above mentioned commit.
Good eyes, fixed! (Not yet pushed, will get there.)
Thanx, Paul
------------------------------------------------------------------------
commit 87b29716cee78c5505039ba933c2f991ed3b1dec
Author: Paul E. McKenney <[email protected]> Date: Sat Sep 2 17:48:39 2017 -0700
memorder: Clarify other-multicopy atomicity
memorder/memorder.tex +24 -18
@@ -1703,32 +1703,32 @@ and other counterintuitive behavior, as discussed in the next section. Threads running on a \emph{multicopy atomic}~\cite{Stone:1995:SP:623262.623912} platform are guaranteed -to agree on the order of writes, even to different variables. +to agree on the order of stores, even to different variables. A useful mental model of such a system is the single-bus architecture shown in Figure~\ref{fig:memorder:Global System Bus And Multi-Copy Atomicity}. -If each write resulted in a message on the bus, and if the bus could -accommodate only one write at a time, then any pair of CPUs would -agree on the order of all writes that they observed. +If each store resulted in a message on the bus, and if the bus could +accommodate only one store at a time, then any pair of CPUs would +agree on the order of all stores that they observed. Unfortunately, building a computer system as shown in the figure, without store buffers or even caches, would result in glacial computation. -CPU vendors have therefore taken one of three approaches: -(1)~Provide store buffers, caches, and the rest and abandon -multicopy atomicity (weakly ordered platforms), -(2)~Provide all those hardware optimizations, and invest many transistors -into preserving multicopy atomicity (TSO platforms), or -(3)~Define a slightly weaker \emph{other-multicopy atomicity} that allows -a given CPU's stores to become visible to that CPU before they become visible -to other CPUs, but in which each of those stores becomes visible to all -the other CPUs simultaneously~\cite{ARMv8A:2017}. -Perhaps there will come a day when all platforms provide some flavor -of multi-copy atomicity, but -in the meantime, non-multicopy-atomic platforms do exist, and so software -does need to deal with them. +CPU vendors interested in providing multicopy atomicity have therefore +instead provided the slightly weaker +\emph{other-multicopy atomicity}~\cite{ARMv8A:2017}, +which excludes the CPU doing a given store from the requirement that all +CPUs agree on the order of all stores. +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''. +Unlike multicopy-atomic platforms, within other-multicopy-atomic platforms, +the CPU doing the store is permitted to observe its +store early, which allows its later loads to obtain the newly stored +value directly from the store buffer. +This in turn improves performance. \QuickQuiz{} Can you give a specific example showing different behavior for - multicopy atomic on the one hand and other multicopy atomic + multicopy atomic on the one hand and other-multicopy atomic on the other? \QuickQuizAnswer{ \begin{listing}[tbp]
@@ -1790,6 +1790,12 @@ exists (1:r1=1 /\ 1:r2=0) which in turn allows the \co{exists} clause to trigger. } \QuickQuizEnd + +Perhaps there will come a day when all platforms provide some flavor +of multi-copy atomicity, but +in the meantime, non-multicopy-atomic platforms do exist, and so software +does need to deal with them. + \begin{listing}[tbp] { \scriptsize \begin{verbbox}[\LstLineNo]
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to [email protected]
More majordomo info at https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=jf_iaSHvJObTbx-siA1ZOg&r=ux41CW3B5BSVxDMRNRWyLbUmPebZc70Kq4AkfdiRGMI&m=4C4QF7BfbGArvD2WxudLaa7Qm9wEkEiEvkE5vbtD8PE&s=jilcBkgE1e1AY60gJfhiKpDB00kxiL--FmmprNHWFw0&e=
Quoted 9 lines · Paul E. McKenney
Quoted 8 lines · Akira Yokosawa
Hi Paul,
I have a comment on the term "other-multicompy atomicity".
It took a while for me to realize that the "other-" stands for "other than self CPU". At first, it sounded like "other type of multicompy atomicity", which looked quite vague.
Quoted 7 lines
Quoted 3 lines
Commit
43236beadb1("memorder: Expand on cumulativity and {other,} multicopy atomicity") helped me to realize your intention. May I suggest to add a footnote on the use of "other-"?I am trying to do a bit too much with that paragraph, aren't I?
How about the patch below?
Please see the comments below.
Quoted 46 lines
Quoted 3 lines
Also, you failed to replace tabs to white spaces in listing added in the above mentioned commit.
Good eyes, fixed! (Not yet pushed, will get there.)
Thanx, Paul
------------------------------------------------------------------------
commit
87b29716cee78c5505039ba933c2f991ed3b1decAuthor: Paul E. McKenney <[email protected]> Date: Sat Sep 2 17:48:39 2017 -0700memorder: Clarify other-multicopy atomicity
Reported-by Akira Yokosawa <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>memorder/memorder.tex +4
-10@@ -1703,32 +1703,32 @@ and other counterintuitive behavior, as discussed in the next section. Threads running on a \emph{multicopy atomic}~\cite{Stone:1995:SP:623262.623912} platform are guaranteed -to agree on the order of writes, even to different variables. +to agree on the order of stores, even to different variables. A useful mental model of such a system is the single-bus architecture shown in Figure~\ref{fig:memorder:Global System Bus And Multi-Copy Atomicity}. -If each write resulted in a message on the bus, and if the bus could -accommodate only one write at a time, then any pair of CPUs would -agree on the order of all writes that they observed. +If each store resulted in a message on the bus, and if the bus could +accommodate only one store at a time, then any pair of CPUs would +agree on the order of all stores that they observed. Unfortunately, building a computer system as shown in the figure, without store buffers or even caches, would result in glacial computation. -CPU vendors have therefore taken one of three approaches: -(1)~Provide store buffers, caches, and the rest and abandon -multicopy atomicity (weakly ordered platforms), -(2)~Provide all those hardware optimizations, and invest many transistors -into preserving multicopy atomicity (TSO platforms), or -(3)~Define a slightly weaker \emph{other-multicopy atomicity} that allows
memorder/memorder.tex and other counterintuitive behavior, as discussed in the next section. · line 1717
Quoted 10 lines
memorder/memorder.tex +3
-7-a given CPU's stores to become visible to that CPU before they become visible -to other CPUs, but in which each of those stores becomes visible to all -the other CPUs simultaneously~\cite{ARMv8A:2017}. -Perhaps there will come a day when all platforms provide some flavor -of multi-copy atomicity, but -in the meantime, non-multicopy-atomic platforms do exist, and so software -does need to deal with them. +CPU vendors interested in providing multicopy atomicity have therefore +instead provided the slightly weaker +\emph{other-multicopy atomicity}~\cite{ARMv8A:2017},
On the ARMv8 multicopy atomicity, I found a paper "Simplifying ARM Concurrency:
Multicopy-atomic Axiomatic and Operational Models for ARMv8" at
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cl.cam.ac.uk_-7Epes20_armv8-2Dmca_armv8-2Dmca-2Ddraft.pdf&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=ux41CW3B5BSVxDMRNRWyLbUmPebZc70Kq4AkfdiRGMI&m=1JFkyKvDbZmHr-CRbzC5HuCgZZCSnpvTioqYoFTfMog&s=BdlEGULkAzO_ibDzx4a3IT6_-zC815dPjOwJa9qPLLo&e= (Draft, July 12, 2017) by Christopher Pulte, et.al. It is a draft, but could also be cited here.
As you know, "ARM ARM" is quite a large document. If you specified where to look
in the manual, it would be even better.
memorder/memorder.tex and other counterintuitive behavior, as discussed in the next section. · line 1722
Quoted 5 lines
memorder/memorder.tex +5
-0+which excludes the CPU doing a given store from the requirement that all +CPUs agree on the order of all stores. +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''.
Yes, now the meaning of "other-" is clear enough.
Thanks, Akira
Quoted 28 lines
memorder/memorder.tex +12
-1+Unlike multicopy-atomic platforms, within other-multicopy-atomic platforms, +the CPU doing the store is permitted to observe its +store early, which allows its later loads to obtain the newly stored +value directly from the store buffer. +This in turn improves performance. \QuickQuiz{} Can you give a specific example showing different behavior for - multicopy atomic on the one hand and other multicopy atomic + multicopy atomic on the one hand and other-multicopy atomic on the other? \QuickQuizAnswer{ \begin{listing}[tbp]@@ -1790,6 +1790,12 @@ exists (1:r1=1 /\ 1:r2=0) which in turn allows the \co{exists} clause to trigger. } \QuickQuizEnd + +Perhaps there will come a day when all platforms provide some flavor +of multi-copy atomicity, but +in the meantime, non-multicopy-atomic platforms do exist, and so software +does need to deal with them. + \begin{listing}[tbp] { \scriptsize \begin{verbbox}[\LstLineNo]
Quoted 75 lines · Akira Yokosawa
Quoted 9 lines · Paul E. McKenney
Quoted 8 lines · Akira Yokosawa
Hi Paul,
I have a comment on the term "other-multicompy atomicity".
It took a while for me to realize that the "other-" stands for "other than self CPU". At first, it sounded like "other type of multicompy atomicity", which looked quite vague.
Quoted 7 lines
Quoted 3 lines
Commit
43236beadb1("memorder: Expand on cumulativity and {other,} multicopy atomicity") helped me to realize your intention. May I suggest to add a footnote on the use of "other-"?I am trying to do a bit too much with that paragraph, aren't I?
How about the patch below?
Please see the comments below.
Quoted 55 lines
Quoted 3 lines
Also, you failed to replace tabs to white spaces in listing added in the above mentioned commit.
Good eyes, fixed! (Not yet pushed, will get there.)
Thanx, Paul
------------------------------------------------------------------------
commit
87b29716cee78c5505039ba933c2f991ed3b1decAuthor: Paul E. McKenney <[email protected]> Date: Sat Sep 2 17:48:39 2017 -0700memorder: Clarify other-multicopy atomicity
Reported-by Akira Yokosawa <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>memorder/memorder.tex +6
-17@@ -1703,32 +1703,32 @@ and other counterintuitive behavior, as discussed in the next section. Threads running on a \emph{multicopy atomic}~\cite{Stone:1995:SP:623262.623912} platform are guaranteed -to agree on the order of writes, even to different variables. +to agree on the order of stores, even to different variables. A useful mental model of such a system is the single-bus architecture shown in Figure~\ref{fig:memorder:Global System Bus And Multi-Copy Atomicity}. -If each write resulted in a message on the bus, and if the bus could -accommodate only one write at a time, then any pair of CPUs would -agree on the order of all writes that they observed. +If each store resulted in a message on the bus, and if the bus could +accommodate only one store at a time, then any pair of CPUs would +agree on the order of all stores that they observed. Unfortunately, building a computer system as shown in the figure, without store buffers or even caches, would result in glacial computation. -CPU vendors have therefore taken one of three approaches: -(1)~Provide store buffers, caches, and the rest and abandon -multicopy atomicity (weakly ordered platforms), -(2)~Provide all those hardware optimizations, and invest many transistors -into preserving multicopy atomicity (TSO platforms), or -(3)~Define a slightly weaker \emph{other-multicopy atomicity} that allows -a given CPU's stores to become visible to that CPU before they become visible -to other CPUs, but in which each of those stores becomes visible to all -the other CPUs simultaneously~\cite{ARMv8A:2017}. -Perhaps there will come a day when all platforms provide some flavor -of multi-copy atomicity, but -in the meantime, non-multicopy-atomic platforms do exist, and so software -does need to deal with them. +CPU vendors interested in providing multicopy atomicity have therefore +instead provided the slightly weaker
Quoted 8 lines
memorder/memorder.tex and other counterintuitive behavior, as discussed in the next section. · line 1717
Quoted 1 line
memorder/memorder.tex +1
-0+\emph{other-multicopy atomicity}~\cite{ARMv8A:2017},On the ARMv8 multicopy atomicity, I found a paper "Simplifying ARM Concurrency:
Multicopy-atomic Axiomatic and Operational Models for ARMv8" at
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cl.cam.ac.uk_-7Epes20_armv8-2Dmca_armv8-2Dmca-2Ddraft.pdf&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=ux41CW3B5BSVxDMRNRWyLbUmPebZc70Kq4AkfdiRGMI&m=1JFkyKvDbZmHr-CRbzC5HuCgZZCSnpvTioqYoFTfMog&s=BdlEGULkAzO_ibDzx4a3IT6_-zC815dPjOwJa9qPLLo&e= (Draft, July 12, 2017) by Christopher Pulte, et.al. It is a draft, but could also be cited here.
As you know, "ARM ARM" is quite a large document. If you specified where to look
in the manual, it would be even better.
Section B2.3, which I have now included in the citation. Please see below for updated patch.
Quoted 7 lines
memorder/memorder.tex and other counterintuitive behavior, as discussed in the next section. · line 1722
Quoted 5 lines
memorder/memorder.tex +5
-0+which excludes the CPU doing a given store from the requirement that all +CPUs agree on the order of all stores. +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''.Yes, now the meaning of "other-" is clear enough.
Glad it helped!
Thanx, Paul
------------------------------------------------------------------------
commit 8223c00857dca7eef47015744b77c126d0c8626e
Author: Paul E. McKenney <[email protected]> Date: Sat Sep 2 17:48:39 2017 -0700
memorder: Clarify other-multicopy atomicity
memorder/memorder.tex +24 -18
@@ -1703,32 +1703,32 @@ and other counterintuitive behavior, as discussed in the next section. Threads running on a \emph{multicopy atomic}~\cite{Stone:1995:SP:623262.623912} platform are guaranteed -to agree on the order of writes, even to different variables. +to agree on the order of stores, even to different variables. A useful mental model of such a system is the single-bus architecture shown in Figure~\ref{fig:memorder:Global System Bus And Multi-Copy Atomicity}. -If each write resulted in a message on the bus, and if the bus could -accommodate only one write at a time, then any pair of CPUs would -agree on the order of all writes that they observed. +If each store resulted in a message on the bus, and if the bus could +accommodate only one store at a time, then any pair of CPUs would +agree on the order of all stores that they observed. Unfortunately, building a computer system as shown in the figure, without store buffers or even caches, would result in glacial computation. -CPU vendors have therefore taken one of three approaches: -(1)~Provide store buffers, caches, and the rest and abandon -multicopy atomicity (weakly ordered platforms), -(2)~Provide all those hardware optimizations, and invest many transistors -into preserving multicopy atomicity (TSO platforms), or -(3)~Define a slightly weaker \emph{other-multicopy atomicity} that allows -a given CPU's stores to become visible to that CPU before they become visible -to other CPUs, but in which each of those stores becomes visible to all -the other CPUs simultaneously~\cite{ARMv8A:2017}. -Perhaps there will come a day when all platforms provide some flavor -of multi-copy atomicity, but -in the meantime, non-multicopy-atomic platforms do exist, and so software -does need to deal with them. +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. +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''. +Unlike multicopy-atomic platforms, within other-multicopy-atomic platforms, +the CPU doing the store is permitted to observe its +store early, which allows its later loads to obtain the newly stored +value directly from the store buffer. +This in turn improves performance. \QuickQuiz{} Can you give a specific example showing different behavior for - multicopy atomic on the one hand and other multicopy atomic + multicopy atomic on the one hand and other-multicopy atomic on the other? \QuickQuizAnswer{ \begin{listing}[tbp]
@@ -1790,6 +1790,12 @@ exists (1:r1=1 /\ 1:r2=0) which in turn allows the \co{exists} clause to trigger. } \QuickQuizEnd + +Perhaps there will come a day when all platforms provide some flavor +of multi-copy atomicity, but +in the meantime, non-multicopy-atomic platforms do exist, and so software +does need to deal with them. + \begin{listing}[tbp] { \scriptsize \begin{verbbox}[\LstLineNo]
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to [email protected]
More majordomo info at https://urldefense.proofpoint.com/v2/url?u=http-3A__vger.kernel.org_majordomo-2Dinfo.html&d=DwIBAg&c=jf_iaSHvJObTbx-siA1ZOg&r=ux41CW3B5BSVxDMRNRWyLbUmPebZc70Kq4AkfdiRGMI&m=Q7EVeNleJycyxaIDU8zrQ-TvAloij0JpWYOZrXIKx4c&s=etV_KUVGGzv0WanXWYzQHz5KX51L3c3orpwBfwRCyvY&e=
Quoted 85 lines · Paul E. McKenney
Quoted 75 lines · Akira Yokosawa
Quoted 9 lines · Paul E. McKenney
Quoted 8 lines · Akira Yokosawa
Hi Paul,
I have a comment on the term "other-multicompy atomicity".
It took a while for me to realize that the "other-" stands for "other than self CPU". At first, it sounded like "other type of multicompy atomicity", which looked quite vague.
Quoted 7 lines
Quoted 3 lines
Commit
43236beadb1("memorder: Expand on cumulativity and {other,} multicopy atomicity") helped me to realize your intention. May I suggest to add a footnote on the use of "other-"?I am trying to do a bit too much with that paragraph, aren't I?
How about the patch below?
Please see the comments below.
Quoted 55 lines
Quoted 3 lines
Also, you failed to replace tabs to white spaces in listing added in the above mentioned commit.
Good eyes, fixed! (Not yet pushed, will get there.)
Thanx, Paul
------------------------------------------------------------------------
commit
87b29716cee78c5505039ba933c2f991ed3b1decAuthor: Paul E. McKenney <[email protected]> Date: Sat Sep 2 17:48:39 2017 -0700memorder: Clarify other-multicopy atomicity
Reported-by Akira Yokosawa <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>memorder/memorder.tex +6
-17@@ -1703,32 +1703,32 @@ and other counterintuitive behavior, as discussed in the next section. Threads running on a \emph{multicopy atomic}~\cite{Stone:1995:SP:623262.623912} platform are guaranteed -to agree on the order of writes, even to different variables. +to agree on the order of stores, even to different variables. A useful mental model of such a system is the single-bus architecture shown in Figure~\ref{fig:memorder:Global System Bus And Multi-Copy Atomicity}. -If each write resulted in a message on the bus, and if the bus could -accommodate only one write at a time, then any pair of CPUs would -agree on the order of all writes that they observed. +If each store resulted in a message on the bus, and if the bus could +accommodate only one store at a time, then any pair of CPUs would +agree on the order of all stores that they observed. Unfortunately, building a computer system as shown in the figure, without store buffers or even caches, would result in glacial computation. -CPU vendors have therefore taken one of three approaches: -(1)~Provide store buffers, caches, and the rest and abandon -multicopy atomicity (weakly ordered platforms), -(2)~Provide all those hardware optimizations, and invest many transistors -into preserving multicopy atomicity (TSO platforms), or -(3)~Define a slightly weaker \emph{other-multicopy atomicity} that allows -a given CPU's stores to become visible to that CPU before they become visible -to other CPUs, but in which each of those stores becomes visible to all -the other CPUs simultaneously~\cite{ARMv8A:2017}. -Perhaps there will come a day when all platforms provide some flavor -of multi-copy atomicity, but -in the meantime, non-multicopy-atomic platforms do exist, and so software -does need to deal with them. +CPU vendors interested in providing multicopy atomicity have therefore +instead provided the slightly weakerQuoted 8 lines
memorder/memorder.tex and other counterintuitive behavior, as discussed in the next section. · line 1717
Quoted 1 line
memorder/memorder.tex +1
-0+\emph{other-multicopy atomicity}~\cite{ARMv8A:2017},On the ARMv8 multicopy atomicity, I found a paper "Simplifying ARM Concurrency:
Multicopy-atomic Axiomatic and Operational Models for ARMv8" at
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cl.cam.ac.uk_-7Epes20_armv8-2Dmca_armv8-2Dmca-2Ddraft.pdf&d=DwICaQ&c=jf_iaSHvJObTbx-siA1ZOg&r=ux41CW3B5BSVxDMRNRWyLbUmPebZc70Kq4AkfdiRGMI&m=1JFkyKvDbZmHr-CRbzC5HuCgZZCSnpvTioqYoFTfMog&s=BdlEGULkAzO_ibDzx4a3IT6_-zC815dPjOwJa9qPLLo&e= (Draft, July 12, 2017) by Christopher Pulte, et.al. It is a draft, but could also be cited here.
As you know, "ARM ARM" is quite a large document. If you specified where to look
in the manual, it would be even better.
Quoted 2 lines
Section B2.3, which I have now included in the citation. Please see below for updated patch.
Looks good!
Thanks, Akira
Quoted 94 lines
Quoted 8 lines
memorder/memorder.tex and other counterintuitive behavior, as discussed in the next section. · line 1722
Quoted 6 lines
memorder/memorder.tex +5
-0+which excludes the CPU doing a given store from the requirement that all +CPUs agree on the order of all stores. +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''.Yes, now the meaning of "other-" is clear enough.
Glad it helped!
Thanx, Paul
------------------------------------------------------------------------
commit
8223c00857dca7eef47015744b77c126d0c8626eAuthor: Paul E. McKenney <[email protected]> Date: Sat Sep 2 17:48:39 2017 -0700memorder: Clarify other-multicopy atomicity
Reported-by Akira Yokosawa <[email protected]>Signed-off-by Paul E. McKenney <[email protected]>memorder/memorder.tex +24
-18@@ -1703,32 +1703,32 @@ and other counterintuitive behavior, as discussed in the next section. Threads running on a \emph{multicopy atomic}~\cite{Stone:1995:SP:623262.623912} platform are guaranteed -to agree on the order of writes, even to different variables. +to agree on the order of stores, even to different variables. A useful mental model of such a system is the single-bus architecture shown in Figure~\ref{fig:memorder:Global System Bus And Multi-Copy Atomicity}. -If each write resulted in a message on the bus, and if the bus could -accommodate only one write at a time, then any pair of CPUs would -agree on the order of all writes that they observed. +If each store resulted in a message on the bus, and if the bus could +accommodate only one store at a time, then any pair of CPUs would +agree on the order of all stores that they observed. Unfortunately, building a computer system as shown in the figure, without store buffers or even caches, would result in glacial computation. -CPU vendors have therefore taken one of three approaches: -(1)~Provide store buffers, caches, and the rest and abandon -multicopy atomicity (weakly ordered platforms), -(2)~Provide all those hardware optimizations, and invest many transistors -into preserving multicopy atomicity (TSO platforms), or -(3)~Define a slightly weaker \emph{other-multicopy atomicity} that allows -a given CPU's stores to become visible to that CPU before they become visible -to other CPUs, but in which each of those stores becomes visible to all -the other CPUs simultaneously~\cite{ARMv8A:2017}. -Perhaps there will come a day when all platforms provide some flavor -of multi-copy atomicity, but -in the meantime, non-multicopy-atomic platforms do exist, and so software -does need to deal with them. +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. +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''. +Unlike multicopy-atomic platforms, within other-multicopy-atomic platforms, +the CPU doing the store is permitted to observe its +store early, which allows its later loads to obtain the newly stored +value directly from the store buffer. +This in turn improves performance. \QuickQuiz{} Can you give a specific example showing different behavior for - multicopy atomic on the one hand and other multicopy atomic + multicopy atomic on the one hand and other-multicopy atomic on the other? \QuickQuizAnswer{ \begin{listing}[tbp]@@ -1790,6 +1790,12 @@ exists (1:r1=1 /\ 1:r2=0) which in turn allows the \co{exists} clause to trigger. } \QuickQuizEnd + +Perhaps there will come a day when all platforms provide some flavor +of multi-copy atomicity, but +in the meantime, non-multicopy-atomic platforms do exist, and so software +does need to deal with them. + \begin{listing}[tbp] { \scriptsize \begin{verbbox}[\LstLineNo]