Messages in this thread | | | Date | Mon, 27 Apr 2015 22:37:05 +0200 | From | Pavel Machek <> | Subject | Re: Revised futex(2) man page for review |
| |
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
| |