future/tm: Sequence locking as practical STM

Signed-off-by: Paul E. McKenney <paulmck@kernel.org>

1 files changed, 10 insertions, 5 deletions

diff --git a/future/tm.tex b/future/tm.tex
index 4af2da8d..e41ed685 100644
--- a/future/tm.tex
+++ b/future/tm.tex
@@ -1204,10 +1204,10 @@ And vice versa.
 	for those rare cases featuring the many silly corner cases listed
 	in this silly section???
 }\QuickQuizAnswer{
-	The year 2005 just called, and it says that it wants its
-	incandescent TM marketing hype back.
+	The year 2005 just called, and it wants its incandescent TM
+	marketing hype back.
 
-	In the year 2021, TM still has significant proving to do,
+	In the year 2023, TM still has significant proving to do,
 	even with the advent of HTM, which is covered in the
 	upcoming
 	\cref{sec:future:Hardware Transactional Memory}.
@@ -1262,5 +1262,10 @@ fig:future:The STM Reality: Realtime Response}.\footnote{
 Less fanciful STM retrospectives are also
 available~\cite{JoeDuffy2010RetroTM,JoeDuffy2010RetroTM2}.
 
-Some commercially available hardware supports restricted variants of
-HTM, which are addressed in the following section.
+Alternatively, one might argue that sequence locking
+(\cref{sec:defer:Sequence Locks}) constitutes a restricted form of
+STM that is heavily used in practice.
+
+Whether or not sequence locking is considered to be the standard bearer
+for STM in actual practice, some commercially available hardware supports
+restricted variants of HTM, which are addressed in the following section.