diff options
| author | SeongJae Park <sj38.park@gmail.com> | 2023-12-02 09:26:10 -0800 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2023-12-02 11:25:42 -0800 |
| commit | 87143226909eac42c3b58a9526ba20bcbf84a8d4 (patch) | |
| tree | ff66764e903a4202fbf1149d0541878c7792ca2a | |
| parent | 06087f88bbdb463e809804b11248887aff5d0cad (diff) | |
| download | perfbook-87143226909eac42c3b58a9526ba20bcbf84a8d4.tar.gz | |
future/tm: Consistently add dash between reader and writer of reader-writer lock
The text is using 'reader-writer lock' consistently, but a sentence in
tm.tex is missing the dash. Add it.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
| -rw-r--r-- | future/tm.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/future/tm.tex b/future/tm.tex index 8b8efa98..db08bcc6 100644 --- a/future/tm.tex +++ b/future/tm.tex @@ -864,7 +864,7 @@ Here are some options available to TM: \item Use TM strictly as an optimization in lock-based systems, as was done by the TxLinux~\cite{ChistopherJRossbach2007a} group, and as has been done by more recent work using TM to elide - reader writer locks~\cite{PascalFelber2016rwlockElision}. + reader-writer locks~\cite{PascalFelber2016rwlockElision}. This approach seems sound, at least on \Power{8} CPUs~\cite{Le:2015:TMS:3266491.3266500}, but leaves the locking design constraints (such as the need to avoid deadlock) firmly |