This commit fixes trivial typos.
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
locking/locking.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/locking/locking.tex b/locking/locking.tex
index a313284..e8ff812 100644
--- a/locking/locking.tex
+++ b/locking/locking.tex
@@ -242,7 +242,7 @@ containing locks from both the library and the caller.
deadlock cycle involving both caller and library locks.
\item If one of the library functions returns a pointer to
a lock that is acquired by the caller, and if the
- caller acquires one if its locks while holding the
+ caller acquires one of its locks while holding the
library's lock, we could again have a deadlock
cycle involving both caller and library locks.
\item If one of the library functions acquires a lock and
@@ -1599,7 +1599,7 @@ Either way, line~21 releases the root \co{rcu_node} structure's
This function illustrates the not-uncommon pattern of hierarchical
locking.
This pattern is quite difficult to implement using RAII locking,
-just like the interator encapsulation noted earlier,
+just like the iterator encapsulation noted earlier,
and so the lock/unlock primitives will be needed for the foreseeable
future.
@@ -1690,7 +1690,7 @@ Line~14 atomically exchanges the value zero (``unlocked'') into
the lock, thus marking it as having been released.
\QuickQuiz{}
- Why not simply store zero into the lock word on line 14 of
+ Why not simply store zero into the lock word on line~14 of
Figure~\ref{fig:locking:Sample Lock Based on Atomic Exchange}?
\QuickQuizAnswer{
This can be a legitimate implementation, but only if
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
