Lines Matching refs:section

32 Section 1, though most readers will profit by reading this section at
41 So, start with the section that makes the most sense to you and your
138 	entering an RCU read-side critical section.  It is illegal
139 	to block while in an RCU read-side critical section, though
142 	accessed during an RCU read-side critical section is guaranteed to
143 	remain unreclaimed for the full duration of that critical section.
152 	exiting an RCU read-side critical section.  Note that RCU
181 	section completes.  For one thing, there might well be scheduling
192 	and is described in more detail in a later section.  Instead of
262 	only within the enclosing RCU read-side critical section.
273 	Holding a reference from one RCU read-side critical section
275 	one lock-based critical section to another!  Similarly,
276 	using a reference outside of the critical section in which
354 This section shows a simple use of the core RCU API to protect a
419 o	Within an RCU read-side critical section, use rcu_dereference()
517 The summary of advice is the same as for the previous section, except
539 production-quality implementations in the Linux kernel.  This section
556 This section presents a "toy" RCU implementation that is based on
560 one read-side critical section to another.
624 This section presents a "toy" RCU implementation that is based on
628 are the same as those shown in the preceding section, so they are omitted.
658 section.  Therefore, if a given CPU executes a context switch, we know
672 		critical section, what the heck do you do in
964 		consider task A in an RCU read-side critical section
1002 		critical section, what the heck do you do in