[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1606241151500.5839@nanos>
Date: Fri, 24 Jun 2016 11:52:07 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
cc: Darren Hart <dvhart@...radead.org>,
Matthieu CASTET <matthieu.castet@...rot.com>,
linux-kernel@...r.kernel.org, Darren Hart <dvhart@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Davidlohr Bueso <dave@...olabs.net>,
Eric Dumazet <dada1@...mosbay.com>
Subject: Re: futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op
On Fri, 24 Jun 2016, Michael Kerrisk (man-pages) wrote:
> By the way, I just realized something that wasn't initially obvious
> to me, and documented it in the futex(2) man page:
>
> Note: for FUTEX_WAIT, timeout is interpreted as a
> relative value. This differs from other futex oper‐
> ations, where timeout is interpreted as an absolute
> value. To obtain the equivalent of FUTEX_WAIT with
> an absolute timeout, employ FUTEX_WAIT_BITSET with
> val3 specified as FUTEX_BITSET_MATCH_ANY.
>
> Okay?
Yes.
Powered by blists - more mailing lists