Lines Matching refs:again

65 to understand, let's use the previous example, with processes A, B, and C again.
172 And once again, to show how this can grow I will show the merging chains
173 again.
278 	/* do something again */
286 in func4 in the "do something again" area, we have a locking that follows:
484 wait_lock, and continue the loop again.  On the next iteration of the
506       task and continue the loop, doing the end of PI chain check again.
515       try again.
535 process.  What if the higher priority process wants to take that mutex again.
542 penalized if it tries to take that mutex again.  If the new owner of the
650 Once again we try to take the mutex.  This will usually fail the first time
694 In any of these cases, we continue the loop and once again try to grab the
711 the rt_mutex_adjust_prio_chain needs to be executed again on the owner,