diff options
| author | Akira Yokosawa <akiyks@gmail.com> | 2021-03-21 00:23:13 +0900 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2021-03-20 11:47:11 -0700 |
| commit | 658b00b2a0fa92aafaa714bdd8484fd0c3763304 (patch) | |
| tree | 1677a842c25078f559ba0792551d20ddbc6cfd10 | |
| parent | 4371a4044c2ec44b8a247424abd2fc75747cc913 (diff) | |
| download | perfbook-658b00b2a0fa92aafaa714bdd8484fd0c3763304.tar.gz | |
together/refcnt: Adjust tense with 'have released'
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
| -rw-r--r-- | together/refcnt.tex | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/together/refcnt.tex b/together/refcnt.tex index 829af167..599ae5f0 100644 --- a/together/refcnt.tex +++ b/together/refcnt.tex @@ -257,7 +257,7 @@ and any needed memory barriers or disabling of compiler optimizations will be provided by the hazard-pointers or RCU infrastructure. Therefore, if two CPUs release the final two references concurrently, the actual cleanup will be deferred until both CPUs have released their hazard -pointers or exits their RCU read-side critical sections, respectively. +pointers or exited their RCU read-side critical sections, respectively. \QuickQuiz{ Why isn't it necessary to guard against cases where one CPU |