From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751211AbcFXJyO (ORCPT ); Fri, 24 Jun 2016 05:54:14 -0400 Received: from www.linutronix.de ([62.245.132.108]:51739 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750853AbcFXJyN (ORCPT ); Fri, 24 Jun 2016 05:54:13 -0400 Date: Fri, 24 Jun 2016 11:52:07 +0200 (CEST) From: Thomas Gleixner To: "Michael Kerrisk (man-pages)" cc: Darren Hart , Matthieu CASTET , linux-kernel@vger.kernel.org, Darren Hart , Peter Zijlstra , Davidlohr Bueso , Eric Dumazet Subject: Re: futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op In-Reply-To: Message-ID: References: <20160620162652.2c4619c3@perruche.parrot.biz> <20160623044828.GA3379@f23x64.localdomain> <520d203a-83ad-0277-79d5-2209d6853628@gmail.com> <20160623161643.GA106079@f23x64.localdomain> <20160623182821.GB106079@f23x64.localdomain> <20160623195515.GD106079@f23x64.localdomain> <20160623203144.GE106079@f23x64.localdomain> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1684984373-1466761928=:5839" X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1684984373-1466761928=:5839 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT 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. --8323329-1684984373-1466761928=:5839--