Some sentences on toyrcu.tex is missing parentheses for
rcu_quiescent_state(). Add those.
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
appendix/toyrcu/toyrcu.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/appendix/toyrcu/toyrcu.tex b/appendix/toyrcu/toyrcu.tex
index 4083f9f0..a33ccdb3 100644
--- a/appendix/toyrcu/toyrcu.tex
+++ b/appendix/toyrcu/toyrcu.tex
@@ -1447,13 +1447,13 @@ re-ordered with the \clnrefrange{gp1}{gp2}.
\begin{fcvref}[ln:defer:rcu_qs:read_lock_unlock:qs]
Doesn't the additional memory barrier shown on \clnref{mb2} of
\cref{lst:app:toyrcu:Quiescent-State-Based RCU Read Side}
- greatly increase the overhead of \co{rcu_quiescent_state}?
+ greatly increase the overhead of \co{rcu_quiescent_state()}?
\end{fcvref}
}\QuickQuizAnswer{
\begin{fcvref}[ln:defer:rcu_qs:read_lock_unlock:qs]
Indeed it does!
An application using this implementation of RCU should therefore
- invoke \co{rcu_quiescent_state} sparingly, instead using
+ invoke \co{rcu_quiescent_state()} sparingly, instead using
\co{rcu_read_lock()} and \co{rcu_read_unlock()} most of the
time.
@@ -1574,7 +1574,7 @@ certain types of library functions.
effect extended beyond the enclosing
\co{rcu_read_lock()} and \co{rcu_read_unlock()}, out to
the previous and next call to \co{rcu_quiescent_state()}.
- This \co{rcu_quiescent_state} can be thought of as an
+ This \co{rcu_quiescent_state()} can be thought of as an
\co{rcu_read_unlock()} immediately followed by an
\co{rcu_read_lock()}.
--
2.17.1
