Lines Matching full:might

112 	can now be speculated, such that it might happen before the
194 	might provide, especially if you are making use of feedback-based
255 You might be surprised that the outcome (r1 == 143 && r2 == 44) is possible,
256 but you should not be.  After all, the updater might have been invoked
322 first pointer might be.  This lack of knowledge prevents the compiler
323 from carrying out optimizations that otherwise might destroy the ordering
327 But without rcu_dereference(), the compiler knows more than you might
389 2.	If the access might be within an RCU read-side critical section
397 3.	If the access might be within an RCU read-side critical section
416 	is appropriate.  In addition, rcu_dereference_raw() might be
418 	complex, except that a better approach in that case might be to
425 	might expect given the number of uses in the current kernel.
442 If register pressure is high, the compiler might optimize "p" out
454 of pointers, which also might fatally disappoint your code.
469 and friends.  For example, ->rcu_protected_pointer might be declared as