diff options
| author | Alan Huang <mmpgouride@gmail.com> | 2023-06-07 11:48:38 +0000 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2023-06-08 11:30:57 -0700 |
| commit | 0fdc786aab4f7f18d78e88f6686d2f451196a0c6 (patch) | |
| tree | e207a78b4f0fe938853f4a00a540030dfee2a7e9 | |
| parent | 9bad825f5d1950c0ed120b4667e34ee6d4625e5c (diff) | |
| download | perfbook-0fdc786aab4f7f18d78e88f6686d2f451196a0c6.tar.gz | |
advsync: Fix typos
Signed-off-by: Alan Huang <mmpgouride@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
| -rw-r--r-- | advsync/rt.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/advsync/rt.tex b/advsync/rt.tex index 8e0347b0..c4d9c3c2 100644 --- a/advsync/rt.tex +++ b/advsync/rt.tex @@ -1228,7 +1228,7 @@ read-side critical section and both the \co{rt_read_unlock()} and the This is necessary because non-realtime kernels' reader-writer locking functions disable preemption across their critical sections, and there really are reader-writer locking use cases that rely on the fact -that \co{synchronize_rcu()} will therefore wait for all pre-exiting +that \co{synchronize_rcu()} will therefore wait for all pre-existing reader-writer-lock critical sections to complete. Let this be a lesson to you: Understanding what your users really need is critically important to @@ -1745,7 +1745,7 @@ These constraints include: \end{enumerate} \QuickQuiz{ - I couldn't help but spot the word ``includes'' before this list. + I couldn't help but spot the word ``include'' before this list. Are there other constraints? }\QuickQuizAnswer{ Indeed there are, and lots of them. |