Skip to content

Commit e15aed4

Browse files
paulmckrcufbq
authored andcommitted
doc: Update checklist.rst discussion of callback execution
This commit completes the list of call_rcu*() functions that are not guaranteed to have their callbacks executing on the same CPU. While in the area, fix an unrelated typo. Signed-off-by: Paul E. McKenney <paulmck@kernel.org> Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
1 parent 56823e9 commit e15aed4

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

Documentation/RCU/checklist.rst

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -383,16 +383,17 @@ over a rather long period of time, but improvements are always welcome!
383383
must use whatever locking or other synchronization is required
384384
to safely access and/or modify that data structure.
385385

386-
Do not assume that RCU callbacks will be executed on the same
387-
CPU that executed the corresponding call_rcu() or call_srcu().
388-
For example, if a given CPU goes offline while having an RCU
389-
callback pending, then that RCU callback will execute on some
390-
surviving CPU. (If this was not the case, a self-spawning RCU
391-
callback would prevent the victim CPU from ever going offline.)
392-
Furthermore, CPUs designated by rcu_nocbs= might well *always*
393-
have their RCU callbacks executed on some other CPUs, in fact,
394-
for some real-time workloads, this is the whole point of using
395-
the rcu_nocbs= kernel boot parameter.
386+
Do not assume that RCU callbacks will be executed on
387+
the same CPU that executed the corresponding call_rcu(),
388+
call_srcu(), call_rcu_tasks(), call_rcu_tasks_rude(), or
389+
call_rcu_tasks_trace(). For example, if a given CPU goes offline
390+
while having an RCU callback pending, then that RCU callback
391+
will execute on some surviving CPU. (If this was not the case,
392+
a self-spawning RCU callback would prevent the victim CPU from
393+
ever going offline.) Furthermore, CPUs designated by rcu_nocbs=
394+
might well *always* have their RCU callbacks executed on some
395+
other CPUs, in fact, for some real-time workloads, this is the
396+
whole point of using the rcu_nocbs= kernel boot parameter.
396397

397398
In addition, do not assume that callbacks queued in a given order
398399
will be invoked in that order, even if they all are queued on the

0 commit comments

Comments
 (0)