futex.2: Rework the description of FUTEX_LOCK_PI2

Note the use of FUTEX_CLOCK_REALTIME for selecting the clock,
and eliminate repetition of details already covered in the
description of FUTEX_LOCK_PI.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2021-08-09 02:07:26 +02:00
parent eeeee81162
commit 69bc3836cc
1 changed files with 14 additions and 14 deletions

View File

@ -1130,22 +1130,22 @@ arguments are ignored.
.TP
.BR FUTEX_LOCK_PI2 " (since Linux 5.14)"
.\" commit bf22a6976897977b0a3f1aeba6823c959fc4fdae
This operation works similar to
.BR FUTEX_LOCK_PI .
The only difference is the
This operation is the same as
.BR FUTEX_LOCK_PI ,
except that the clock against which
.I timeout
argument.
.B FUTEX_LOCK_PI2
has support for selectable clocks.
.IP
If
is measured is selectable.
By default, the (absolute) timeout specified in
.I timeout
is not NULL, the structure it points to specifies
an absolute timeout.
If
.I timeout
is NULL, the operation can block indefinitely.
.IP
is measured againt the
.B CLOCK_MONOTONIC
clock, but if the
.B FUTEX_CLOCK_REALTIME
flag is specified in
.IR futex_op ,
then the timeout is measured against the
.B CLOCK_REALTIME
clock.
.\"
.\""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
.\"