>From 9aac20a120daf460b1046cb234e8eddd1171271b Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiysw@xxxxxxxxx>
Date: Fri, 15 Apr 2016 23:20:36 +0900
Subject: [PATCH 2/3] advsync: Add necessary blank lines around minipages
In the `Pair-Wise Memory Barriers: Portable Combinations`
subsubsection, we need blank lines before and after minipages
that embody code snippet tables. Without them, minipages are
forced to be placed in strange ways. This commit adds those
necessary blank lines.
Also it adds "\scriptsize" commands to the minipages for their
consistency with the one in the previous subsubsection.
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
advsync/memorybarriers.tex | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
index 965718c..0ef020f 100644
--- a/advsync/memorybarriers.tex
+++ b/advsync/memorybarriers.tex
@@ -565,9 +565,11 @@ pairings that portable software may depend on.
by a memory barrier, while a second CPU executes a pair
of stores also separated by a memory barrier, as follows
(both A and B are initially equal to zero):
+
\vspace{5pt}
\begin{minipage}[t]{\columnwidth}
\tt
+ \scriptsize
\begin{tabular}{l|l}
CPU 1 & CPU 2 \\
\hline
@@ -577,6 +579,7 @@ pairings that portable software may depend on.
\end{tabular}
\end{minipage}
\vspace{5pt}
+
After both CPUs have completed executing these code sequences,
if \co{Y==1}, then we must also have \co{X==1}.
In this case, the fact that \co{Y==1} means that
@@ -594,9 +597,11 @@ pairings that portable software may depend on.
In this pairing, each CPU executes a load followed by a
memory barrier followed by a store, as follows
(both A and B are initially equal to zero):
+
\vspace{5pt}
\begin{minipage}[t]{\columnwidth}
\tt
+ \scriptsize
\begin{tabular}{l|l}
CPU 1 & CPU 2 \\
\hline
@@ -606,6 +611,7 @@ pairings that portable software may depend on.
\end{tabular}
\end{minipage}
\vspace{5pt}
+
After both CPUs have completed executing these code sequences,
if \co{X==1}, then we must also have \co{Y==0}.
In this case, the fact that \co{X==1} means that
@@ -628,9 +634,11 @@ pairings that portable software may depend on.
memory barrier followed by a store, while the other CPU
executes a pair of stores separated by a memory barrier,
as follows (both A and B are initially equal to zero):
+
\vspace{5pt}
\begin{minipage}[t]{\columnwidth}
\tt
+ \scriptsize
\begin{tabular}{l|l}
CPU 1 & CPU 2 \\
\hline
@@ -640,6 +648,7 @@ pairings that portable software may depend on.
\end{tabular}
\end{minipage}
\vspace{5pt}
+
After both CPUs have completed executing these code sequences,
if \co{X==1}, then we must also have \co{B==1}.
In this case, the fact that \co{X==1} means that
@@ -710,6 +719,7 @@ keep in mind that they used to be a \emph{lot} harder on some systems!
\vspace{5pt}
\begin{minipage}[t]{\columnwidth}
\tt
+ \scriptsize
\begin{tabular}{l|l}
CPU 1 & CPU 2 \\
\hline
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
