Lines Matching refs:was

17 decisions that were made to implement PI in the manner that was done.
433 was passed by parameter (for the first iteration).  The pi_lock of this task is
473 Note: It is possible that the task was the current top waiter on the mutex,
478 If the task was not the top waiter of the mutex, but it was before we
501       the protection of the mutex's wait_lock, which was not taken yet.
525 What this means is that an owner was chosen by the process releasing the
547 new process is given a mutex that it was blocked on, it is only given
632   mutex actually has waiters, or we clear the flag if it doesn't.  See, it was
671 Since the wait_lock was taken at the entry of the slow lock, we can safely
691   2) we received a signal and was TASK_INTERRUPTIBLE
692   3) we had a timeout and was TASK_INTERRUPTIBLE
710 pi_list of the owner.  If this process was a high priority process, then
781 This document was originally written for 2.6.17-rc3-mm1