>From 8b81634e0268329ecdcad3ce731a33d9d42e0786 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Mon, 19 Mar 2017 23:25:12 +0900
Subject: [PATCH 2/6] whymb: Convert to 'description' (part 2)
This list is also a good candidate to convert to "description".
As labels are printed in bold, colons at the tail of API names
can be removed. Also replace double quotes after labels with
parentheses for consistency with other lists in the Appendix.
\tco{} is safer than \co{} in labels.
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
appendix/whymb/whymemorybarriers.tex | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/appendix/whymb/whymemorybarriers.tex b/appendix/whymb/whymemorybarriers.tex
index bd87ee7..49d29ba 100644
--- a/appendix/whymb/whymemorybarriers.tex
+++ b/appendix/whymb/whymemorybarriers.tex
@@ -1656,18 +1656,18 @@ use of memory barriers is required.
Therefore,
Linux provides a carefully chosen least-common-denominator
set of memory-barrier primitives, which are as follows:
-\begin{itemize}
-\item \co{smp_mb()}: ``memory barrier'' that orders both loads and
+\begin{description}
+\item [\tco{smp_mb()}] (memory barrier) that orders both loads and
stores.
This means that loads and stores preceding the memory barrier
will be committed to memory before any loads and stores
following the memory barrier.
-\item \co{smp_rmb()}: ``read memory barrier'' that orders only loads.
-\item \co{smp_wmb()}: ``write memory barrier'' that orders only stores.
-\item \co{smp_read_barrier_depends()} that forces subsequent operations
+\item [\tco{smp_rmb()}] (read memory barrier) that orders only loads.
+\item [\tco{smp_wmb()}] (write memory barrier) that orders only stores.
+\item [\tco{smp_read_barrier_depends()}] that forces subsequent operations
that depend on prior operations to be ordered.
This primitive is a no-op on all platforms except Alpha.
-\item {\tt mmiowb()} that forces ordering on MMIO writes that are guarded
+\item [\tco{mmiowb()}] that forces ordering on MMIO writes that are guarded
by global spinlocks.
This primitive is a no-op on all platforms on which the memory
barriers in spinlocks already enforce MMIO ordering.
@@ -1675,7 +1675,7 @@ set of memory-barrier primitives, which are as follows:
some (but not all) IA64, FRV, MIPS, and SH systems.
This primitive is relatively new, so relatively few drivers take
advantage of it.
-\end{itemize}
+\end{description}
The \co{smp_mb()}, \co{smp_rmb()}, and \co{smp_wmb()}
primitives also force
the compiler to eschew any optimizations that would have the effect
--
2.7.4
--
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
