Thread (60 messages) 60 messages, 5 authors, 2021-10-17

Re: [PATCH 06/23] futex.2: Document FUTEX_LOCK_PI2

From: Michael Kerrisk (man-pages) <hidden>
Date: 2021-08-09 09:02:12

On Mon, 9 Aug 2021 at 10:14, Kurt Kanzenbach [off-list ref] wrote:
Hi Michael,

On Mon Aug 09 2021, Michael Kerrisk (man-pages) wrote:
quoted
quoted
+.IP
+If
+.I timeout
+is not NULL, the structure it points to specifies
+an absolute timeout.
+If
+.I timeout
+is NULL, the operation can block indefinitely.
The above is the same as FUTEX_LOCK_PI, right? So, it
probably doesn't need repeating.

I've reworked this description to be:

       FUTEX_LOCK_PI2 (since Linux 5.14)
              This operation is the same as FUTEX_LOCK_PI, except that
              the clock against which timeout is measured is selectable.
              By default, the (absolute) timeout specified in timeout is
              measured againt the CLOCK_MONOTONIC clock, but if the
              FUTEX_CLOCK_REALTIME flag is specified in futex_op, then
              the timeout is measured against the CLOCK_REALTIME clock.

Is it okay?
Sounds good.
Okay. Thanks.

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help