mirror of https://github.com/mkerrisk/man-pages
futex.2: Fix discussion of FUTEX_LOCK_PI 'timeout' argument
Reading futex_lock_pi(), it appears that the timeout is *not* interpreted in the same way as for FUTEX_WAKE. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
a8b5b324e3
commit
9ce19cf1b7
13
man2/futex.2
13
man2/futex.2
|
@ -649,11 +649,18 @@ The owner inherits either the priority or the bandwidth of the waiter.
|
||||||
This inheritance follows the lock chain in the case of
|
This inheritance follows the lock chain in the case of
|
||||||
nested locking and performs deadlock detection.
|
nested locking and performs deadlock detection.
|
||||||
|
|
||||||
|
.\" FIXME tglx says "The timeout argument is handled as described in
|
||||||
|
.\" FUTEX_WAIT." However, it appears to me that this is not right.
|
||||||
|
.\" Is the following formulation correct.
|
||||||
The
|
The
|
||||||
.I timeout
|
.I timeout
|
||||||
.\" FIXME Is this true??????????????????????
|
argument provides a timeout for the lock attempt.
|
||||||
argument is handled as described in
|
It is interpreted as an absolute time, measured against the
|
||||||
.BR FUTEX_WAIT .
|
.BR CLOCK_REALTIME
|
||||||
|
clock.
|
||||||
|
If
|
||||||
|
.I timeout
|
||||||
|
is NULL, the operation will block indefinitely.
|
||||||
|
|
||||||
The
|
The
|
||||||
.IR uaddr2 ,
|
.IR uaddr2 ,
|
||||||
|
|
Loading…
Reference in New Issue