Lines Matching refs:call_rcu
185 5. If call_rcu(), or a related primitive such as call_rcu_bh(),
215 7. If the updater uses call_rcu() or synchronize_rcu(), then the
237 8. Although synchronize_rcu() is slower than is call_rcu(), it
241 should be used in preference to call_rcu(). Furthermore,
251 code using call_rcu() should explicitly limit update rate in
255 Ways of gaining this self-limiting property when using call_rcu()
288 d. Use call_rcu_bh() rather than call_rcu(), in order to take
346 expedited forms of the three primitives, namely call_rcu(),
366 the corresponding call_rcu(), call_rcu_bh(), or call_rcu_sched(),
417 15. The whole point of call_rcu(), synchronize_rcu(), and friends
422 destructive operation, and -only- -then- invoke call_rcu(),
446 same object to call_rcu() (or friends) before an RCU
448 passed that same object to call_rcu() (or friends).
458 18. If you register a callback using call_rcu(), call_rcu_bh(),
471 o call_rcu() -> rcu_barrier()
477 to wait for a grace period. In fact, if there are no call_rcu()
482 all pre-existing call_rcu() callbacks, you will need to execute