Lines Matching full:side
138 * rcu_read_lock - mark the beginning of an RCU read-side critical section.
141 * are within RCU read-side critical sections, then the
144 * on one CPU while other CPUs are within RCU read-side critical
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.
199 * a process in RCU read-side critical section must be protected by
200 * disabling softirqs. Read-side critical sections in interrupt context
223 * RCU read-side critical section. This pointer may later
239 * initialized structure that will be dereferenced by RCU read-side
246 * call documents which pointers will be dereferenced by RCU read-side
