Lines Matching full:might

103 	can now be speculated, such that it might happen before the
179 	might provide, especially if you are making use of feedback-based
239 You might be surprised that the outcome (r1 == 143 && r2 == 44) is possible,
240 but you should not be.  After all, the updater might have been invoked
305 first pointer might be.  This lack of knowledge prevents the compiler
306 from carrying out optimizations that otherwise might destroy the ordering
310 But without rcu_dereference(), the compiler knows more than you might
371 2.	If the access might be within an RCU read-side critical section
379 3.	If the access might be within an RCU read-side critical section
398 	is appropriate.  In addition, rcu_dereference_raw() might be
400 	complex, except that a better approach in that case might be to
407 	might expect given the number of uses in the current kernel.
423 If register pressure is high, the compiler might optimize "p" out
435 of pointers, which also might fatally disappoint your code.
450 and friends.  For example, ->rcu_protected_pointer might be declared as