From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965365AbbD0UhL (ORCPT ); Mon, 27 Apr 2015 16:37:11 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:59095 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965114AbbD0UhI (ORCPT ); Mon, 27 Apr 2015 16:37:08 -0400 Date: Mon, 27 Apr 2015 22:37:05 +0200 From: Pavel Machek To: Peter Zijlstra Cc: "Michael Kerrisk (man-pages)" , Thomas Gleixner , Darren Hart , "Carlos O'Donell" , Ingo Molnar , Jakub Jelinek , "linux-man@vger.kernel.org" , lkml , Davidlohr Bueso , Arnd Bergmann , Steven Rostedt , Linux API , Torvald Riegel , Roland McGrath , Darren Hart , Anton Blanchard , Eric Dumazet , bill o gallmeister , Jan Kiszka , Daniel Wagner , Rich Felker , Andy Lutomirski , bert hubert , Rusty Russell , Heinrich Schuchardt Subject: Re: Revised futex(2) man page for review Message-ID: <20150427203705.GE29351@xo-6d-61-c0.localdomain> References: <55166C01.7000803@gmail.com> <20150328114725.GJ27490@worktop.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150328114725.GJ27490@worktop.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! > The FUTEX_WAIT_OP operation is equivalent to execute the follow??? > ing code atomically and totally ordered with respect to other > futex operations on any of the two supplied futex words: "to executing"? > The operation and comparison that are to be performed are > encoded in the bits of the argument val3. Pictorially, the > encoding is: > > +---+---+-----------+-----------+ > |op |cmp| oparg | cmparg | > +---+---+-----------+-----------+ > 4 4 12 12 <== # of bits > :-) > RETURN VALUE > In the event of an error, all operations return -1 and set errno to > indicate the cause of the error. The return value on success depends > on the operation, as described in the following list: Did you say (at the begining) that there is no glibc wrapper? > EINVAL The operation in futex_op is one of those that employs a time??? > out, but the supplied timeout argument was invalid (tv_sec was > less than zero, or tv_nsec was not less than 1000,000,000). 1,000...? > NOTES > Glibc does not provide a wrapper for this system call; call it using > syscall(2). -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html