Lines Matching refs:that
6 A common misconception is that, on UP systems, the call_rcu() primitive
8 is that since there is only one CPU, it should not be necessary to
12 This document presents three examples that demonstrate exactly how bad
18 Suppose that an RCU-based algorithm scans a linked list containing
20 this same list in softirq context. Suppose that the process-context scan
40 Suppose that an RCU-based algorithm again scans a linked list containing
41 elements A, B, and C in process contexts, but that it invokes a function
42 on each element as it is scanned. Suppose further that this function
48 underlying RCU, namely that call_rcu() defers invoking its arguments until
59 Suppose that call_rcu() is invoked while holding a lock, and that the
64 In some cases, it would possible to restructure to code so that
74 so that delaying the call_rcu() until the lock is released
75 requires that the data item be passed up via a common API.
76 It is far better to guarantee that callbacks are invoked
96 Note that it *is* safe for synchronize_rcu() to return immediately on
116 Any lock that is acquired within an RCU callback must be acquired
120 like spin_lock_bh() to acquire the lock. Please note that
126 the callback might be called from a softirq that interrupted
143 that other thread when it started running again.