Lines Matching refs:by

1 Started by Paul Jackson <pj@sgi.com>
18     by the exiting thread.
22 call, and handles contested locking by maintaining a list of waiting
74 entry', at an offset from the 'lock entry' specified by the 'offset'
78 lock variable used by the futex mechanism, in conjunction with
83 For each futex lock currently held by a thread, if it wants this
93 pointer for that task.  The task may retrieve that value later on by
104 robust_futexes used by that thread.  The thread should link those locks
115 entirely by user level code in the contending threads, and by the
119 still held by the departing thread, as described below.
123 lock structures for locks currently held by that thread should be on
127 at different times by any of the threads with access to that region. The
153 'list_op_pending' and the address of each 'lock word' found by walking
163 In the above, bit 31 was set by futex waiters on that lock to indicate
164 they were waiting, and bit 30 is set by the kernel to indicate that the