Lines Matching full:might

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