diff options
author | SeongJae Park <sj38.park@gmail.com> | 2023-12-17 09:41:16 -0800 |
---|---|---|
committer | Paul E. McKenney <paulmck@kernel.org> | 2023-12-30 16:23:22 -0800 |
commit | 8006c40aaff55e94646a04d620c7e03aeedb68c4 (patch) | |
tree | 285d288e27dac0991fc48d276d205046dc706b41 | |
parent | 47951011c01e3853c44334cc6a1af1f1eac64064 (diff) | |
download | perfbook-8006c40aaff55e94646a04d620c7e03aeedb68c4.tar.gz |
appendix/questions/after: Use \qco{} for quoting code
after.tex is using ``...'' for quoting some variables of a code snippet.
Use \qco{} instead.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
-rw-r--r-- | appendix/questions/after.tex | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/appendix/questions/after.tex b/appendix/questions/after.tex index c165eb0e..d6b0dfdf 100644 --- a/appendix/questions/after.tex +++ b/appendix/questions/after.tex @@ -13,15 +13,15 @@ An important non-intuitive issue is that code can be delayed at any point for any amount of time. Consider a producing and a consuming thread that communicate using -a global struct with a timestamp ``t'' and integer fields ``a'', ``b'', -and ``c''. +a global struct with a timestamp \qco{t} and integer fields \qco{a}, \qco{b}, +and \qco{c}. The producer loops recording the current time (in seconds since 1970 in decimal), -then updating the values of ``a'', ``b'', and ``c'', +then updating the values of \qco{a}, \qco{b}, and \qco{c}, as shown in \cref{lst:app:questions:After Producer Function}. The consumer code loops, also recording the current time, but also -copying the producer's timestamp along with the fields ``a'', -``b'', and ``c'', as shown in +copying the producer's timestamp along with the fields \qco{a}, +\qco{b}, and \qco{c}, as shown in \cref{lst:app:questions:After Consumer Function}. At the end of the run, the consumer outputs a list of anomalous recordings, e.g., where time has appeared to go backwards. |