Lines Matching +refs:queue +refs:get +refs:op

37 Note also that it is possible that a barrier may be a no-op for an
94  (*) The things CPUs get up to.
279      we may get any of the following sequences:
293      we may get any one of the following sequences:
303      we may get any of:
537      access queue that accesses of the appropriate type may not cross.
1732      interrupt handler returns with interrupts enabled, you will get a
2036      being unable to get the lock immediately, or due to receiving an unblocked
2415 get the lock again; it instead just waits for its task pointer to be cleared
2442 function has to needlessly get the spinlock again after being woken up.
2735 generate load and store operations which then go into the queue of memory
2736 accesses to be performed.  The core may place these in the queue in any order