summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul E. McKenney <paulmck@kernel.org>2023-06-22 18:13:55 -0700
committerPaul E. McKenney <paulmck@kernel.org>2023-06-22 18:13:55 -0700
commit18a82fca0da45a1487ef359e19d4dded23181e76 (patch)
tree1cced5e8b3491c325891d4d3dc0c082199805447
parent938752216c8de720121a3207158289ceceb74dff (diff)
downloadperfbook-18a82fca0da45a1487ef359e19d4dded23181e76.tar.gz
future/tm: TM-unfriendly operations and composability
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
-rw-r--r--future/tm.tex10
1 files changed, 10 insertions, 0 deletions
diff --git a/future/tm.tex b/future/tm.tex
index e41ed685..b649f3cc 100644
--- a/future/tm.tex
+++ b/future/tm.tex
@@ -81,6 +81,16 @@ This section therefore critiques transactional memory's outside-world
capabilities, focusing on I/O operations, time delays, and persistent
storage.
+And these interactions with the outside world are the rock upon which
+the claims of unconditional TM composability are shattered.
+Yes, you can compose transactions, but only as long as there are no
+intervening TM-unfriendly operations.
+Just as you can compose lock-based critical sections, but only as long
+as doing so does not introduce deadlocks.
+
+In the end, it is unclear whether TM really provides better composability
+than does locking in real-world code.
+
\subsubsection{I/O Operations}
\label{sec:future:I/O Operations}