Lines Matching refs:that

4 A common misconception is that, on UP systems, the call_rcu() primitive
6 is that since there is only one CPU, it should not be necessary to
10 This document presents three examples that demonstrate exactly how bad
16 Suppose that an RCU-based algorithm scans a linked list containing
18 this same list in softirq context.  Suppose that the process-context scan
38 Suppose that an RCU-based algorithm again scans a linked list containing
39 elements A, B, and C in process contexts, but that it invokes a function
40 on each element as it is scanned.  Suppose further that this function
46 underlying RCU, namely that call_rcu() defers invoking its arguments until
55 Suppose that call_rcu() is invoked while holding a lock, and that the
60 In some cases, it would possible to restructure to code so that
70 	so that delaying the call_rcu() until the lock is released
71 	requires that the data item be passed up via a common API.
72 	It is far better to guarantee that callbacks are invoked
109 	Any lock that is acquired within an RCU callback must be
118 	the callback might be called from a softirq that interrupted
135 	that other thread when it started running again.