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
95  (*) The things CPUs get up to.
280      we may get any of the following sequences:
294      we may get any one of the following sequences:
304      we may get any of:
538      access queue that accesses of the appropriate type may not cross.
1735      interrupt handler returns with interrupts enabled, you will get a
2039      being unable to get the lock immediately, or due to receiving an unblocked
2418 get the lock again; it instead just waits for its task pointer to be cleared
2445 function has to needlessly get the spinlock again after being woken up.
2738 generate load and store operations which then go into the queue of memory
2739 accesses to be performed.  The core may place these in the queue in any order