>From 62edb155faac3b554f38b6d5f939cbad3e5030e1 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Tue, 10 Mar 2020 07:58:31 +0900
Subject: [PATCH 3/3] defer/seqlock: Move figure env next to 1st paragraph
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
defer/seqlock.tex | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/defer/seqlock.tex b/defer/seqlock.tex
index 1df6efad..c3a9773f 100644
--- a/defer/seqlock.tex
+++ b/defer/seqlock.tex
@@ -7,13 +7,6 @@
%
\epigraph{It'll be just like starting over.}{\emph{John Lennon}}
-\begin{figure}[tb]
-\centering
-\resizebox{3in}{!}{\includegraphics{cartoons/r-2014-Start-over}}
-\caption{Reader And Uncooperative Sequence Lock}
-\label{fig:defer:Reader And Uncooperative Sequence Lock}
-\end{figure}
-
Sequence locks are used in the Linux kernel for read-mostly data that
must be seen in a consistent state by readers.
However, unlike reader-writer locking, readers do not exclude writers.
@@ -24,6 +17,13 @@ Figure~\ref{fig:defer:Reader And Uncooperative Sequence Lock},
it is important to design code using sequence locks so that readers
very rarely need to retry.
+\begin{figure}[tb]
+\centering
+\resizebox{3in}{!}{\includegraphics{cartoons/r-2014-Start-over}}
+\caption{Reader And Uncooperative Sequence Lock}
+\label{fig:defer:Reader And Uncooperative Sequence Lock}
+\end{figure}
+
\QuickQuiz{
Why isn't this sequence-lock discussion in Chapter~\ref{chp:Locking},
you know, the one on \emph{locking}?
--
2.17.1
