Lines Matching refs:code

18 Since call_rcu() never blocks, this code can safely be used from within
39 We could try placing a synchronize_rcu() in the module-exit code path,
61 Pseudo-code using rcu_barrier() is as follows:
72 call_srcu() on srcu_struct_2, then the following three lines of code
194 The original code for rcu_barrier() was roughly as follows::
229 This code was rewritten in 2008 and several times thereafter, but this
278 the code above illustrates the concepts.
285 code using RCU is in the core kernel rather than in modules. However, if
328 	Note that this was not a problem when the rcu_barrier() code
336 	RCU once again waits on nonpreemptible regions of code.
367 	preemption-disabled regions of code as RCU read-side critical