Lines Matching full:critical
138 * rcu_read_lock - mark the beginning of an RCU read-side critical section.
141 * are within RCU read-side critical sections, then the
143 * CPUs exit their critical sections. Similarly, if call_rcu() is invoked
144 * on one CPU while other CPUs are within RCU read-side critical
146 * until after the all the other CPUs exit their critical sections.
149 * with RCU read-side critical sections. One way that this can happen
151 * read-side critical section, (2) CPU 1 invokes call_rcu() to register
152 * an RCU callback, (3) CPU 0 exits the RCU read-side critical section,
153 * (4) CPU 2 enters a RCU read-side critical section, (5) the RCU
154 * callback is invoked. This is legal, because the RCU read-side critical
160 * RCU read-side critical sections may be nested. Any deferred actions
161 * will be deferred until the outermost RCU read-side critical section
164 * It is illegal to block while in an RCU read-side critical section.
173 * rcu_read_unlock - marks the end of an RCU read-side critical section.
194 * rcu_read_lock_bh - mark the beginning of a softirq-only RCU critical section
199 * a process in RCU read-side critical section must be protected by
200 * disabling softirqs. Read-side critical sections in interrupt context
211 * rcu_read_unlock_bh - marks the end of a softirq-only RCU critical section
223 * RCU read-side critical section. This pointer may later
240 * critical sections. Returns the value assigned.
