Lines Matching full:therefore
32 This document therefore summarizes RCU's requirements, and can be thought
144 <tt>synchronize_rcu()</tt> started, and must therefore also load
146 Therefore, the outcome:
313 Therefore, we clearly need some way to prevent the compiler and the CPU from
734 Therefore, there absolutely must be a full memory barrier between the
843 Therefore, the justification for adding a conditional primitive to
885 It is therefore all too easy to assume that RCU is guaranteeing more
1039 Therefore, the code following
1254 Therefore, even in practice, RCU users must abide by the
1265 They therefore bear repeating:
1289 RCU is therefore obligated to use algorithms that have
1295 RCU must therefore use scalable locking designs.
1297 RCU's use of counters must therefore tolerate counter wrap,
1312 RCU must therefore pay close attention to high-end scalability.
1482 and Linux-kernel RCU implementations must therefore avoid unnecessarily
1538 It may therefore incur several milliseconds of latency in addition to
1651 Therefore, any insertions will be delayed until after
1784 Therefore, RCU must provide a number of mechanisms to promote forward
1820 RCU will therefore invoke <tt>resched_cpu()</tt> on any
1953 Therefore, RCU priority boosting is provided to help deal with this
2067 RCU therefore supplies the <tt>rcu_sysrq_start()</tt> and
2091 Therefore, RCU-protected
2185 RCU must therefore wait for a given CPU to actually come online before
2342 The module-unload functions must therefore cancel any
2356 RCU therefore provides
2359 If a module uses <tt>call_rcu()</tt>, its exit function should therefore
2377 Therefore, if there are no RCU callbacks posted anywhere in the system,
2390 Doesn't <tt>rcu_barrier()</tt> therefore need to wait for
2455 implementation must therefore be written carefully to avoid deadlocks
2508 Therefore, as noted above, if scheduler spinlocks are held across
2589 Therefore, the Linux-kernel definitions of <tt>rcu_read_lock()</tt>
2600 RCU therefore conserves energy by detecting which CPUs are
2659 RCU must therefore track <tt>nohz_full</tt> userspace
2661 RCU must therefore be able to sample state at two points in
2852 It is therefore necessary to exercise caution when packing
2877 RCU must therefore use efficient implementations, especially in its
2890 RCU therefore makes heavy use of a combining tree based on the
2909 Kernels built with <tt>CONFIG_PREEMPT=y</tt> therefore
2925 RCU's scalability and latency must therefore be sufficient for
3005 Much of the material in this section is therefore strictly historical
3078 Much of the material in this section is therefore strictly historical
3088 Therefore, <i>RCU-sched</i> was created, which follows “classic”
3311 and these three APIs are therefore implemented by separate functions