futex.2: Note that the CLOCK_MONOTONIC clock is used for relative timeouts

Verified from inspection of kernel/futex.c::futex_wait().

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2015-01-12 13:47:01 +01:00
parent 1909e523d0
commit 1c952cf53c
1 changed files with 10 additions and 3 deletions

View File

@ -140,8 +140,11 @@ time based on
.BR CLOCK_REALTIME . .BR CLOCK_REALTIME .
If this option is not set, If this option is not set,
the kernel treats the user space supplied timeout as relative time. the kernel treats the user space supplied timeout as relative time,
.\" FIXME a relative time based on what clock? .\" FIXME I added CLOCK_MONOTONIC here. Is it correct?
measured against the
.BR CLOCK_MONOTONIC
clock.
.PP .PP
The operation specified in The operation specified in
.I op .I op
@ -159,7 +162,11 @@ on this futex address.
If the If the
.I timeout .I timeout
argument is non-NULL, its contents specify a relative timeout for the wait. argument is non-NULL, its contents specify a relative timeout for the wait
.\" FIXME I added CLOCK_MONOTONIC here. Is it correct?
measured according to the
.BR CLOCK_MONOTONIC
clock.
(This interval will be rounded up to the system clock granularity, (This interval will be rounded up to the system clock granularity,
and kernel scheduling delays mean that the and kernel scheduling delays mean that the
blocking interval may overrun by a small amount.) blocking interval may overrun by a small amount.)