diff options
author | Paul E. McKenney <paulmck@kernel.org> | 2023-06-09 15:52:59 -0700 |
---|---|---|
committer | Paul E. McKenney <paulmck@kernel.org> | 2023-06-09 15:52:59 -0700 |
commit | 4a36802e54255c4c4d5b423e729bf5fdcce0e807 (patch) | |
tree | e27f57e63f8716706f199fc6fc1c379cc743e80c | |
parent | 0fdc786aab4f7f18d78e88f6686d2f451196a0c6 (diff) | |
download | perfbook-4a36802e54255c4c4d5b423e729bf5fdcce0e807.tar.gz |
Revert "together/applyrcu: Note possibility of lost counts"
This reverts commit 94f01e467566ebfaee77868cc02b747e8950ad0b.
Reported-by: Alan Huang <mmpgouride@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
-rw-r--r-- | together/applyrcu.tex | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/together/applyrcu.tex b/together/applyrcu.tex index a9cbfd22..dee027b9 100644 --- a/together/applyrcu.tex +++ b/together/applyrcu.tex @@ -151,15 +151,6 @@ is invoked by each newly created thread. So, interestingly enough, when adding a new thread, this implementation gets the effect of allocating a new structure, but without actually having to do the allocation. - - \begin{fcvref}[ln:count:count_end_rcu:whole:unreg] - On the other hand, \co{count_unregister_thread()} can result - in the outgoing thread's counts being lost. - This can happen when \co{read_count()} is invoked between - \clnref{null,assign}. - There are efficient ways of avoiding this count loss, but - these are left as an exercise for the reader. - \end{fcvref} }\QuickQuizEnd \begin{fcvref}[ln:count:count_end_rcu:whole:unreg] |