From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Torvald Riegel <triegel@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: mtk.manpages@gmail.com, Peter Zijlstra <peterz@infradead.org>,
Darren Hart <dvhart@linux.intel.com>,
"Carlos O'Donell" <carlos@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Jakub Jelinek <jakub@redhat.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Arnd Bergmann <arnd@arndb.de>,
Steven Rostedt <rostedt@goodmis.org>,
Linux API <linux-api@vger.kernel.org>,
Roland McGrath <roland@hack.frob.com>,
Darren Hart <dvhart@infradead.org>,
Anton Blanchard <anton@samba.org>,
Eric Dumazet <edumazet@google.com>,
bill o gallmeister <bgallmeister@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Daniel Wagner <wagi@monom.org>, Rich Felker <dalias@libc.org>,
Andy Lutomirski <luto@amacapital.net>,
bert hubert <bert.hubert@netherlabs.nl>,
Rusty Russell <rusty@rustcorp.com.au>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: Revised futex(2) man page for review
Date: Mon, 27 Jul 2015 13:10:39 +0200 [thread overview]
Message-ID: <55B611AF.4030600@gmail.com> (raw)
In-Reply-To: <1429093725.2909.29.camel@triegel.csb>
On 04/15/2015 12:28 PM, Torvald Riegel wrote:
> On Tue, 2015-04-14 at 23:40 +0200, Thomas Gleixner wrote:
>> On Sat, 28 Mar 2015, Peter Zijlstra wrote:
>>> On Sat, Mar 28, 2015 at 09:53:21AM +0100, Michael Kerrisk (man-pages) wrote:
>>>> So, please take a look at the page below. At this point,
>>>> I would most especially appreciate help with the FIXMEs.
>>>
>>> For people who cannot read that troff gibberish (me)..
>>
>> Ditto :)
>>
>>> NOTES
>>> Glibc does not provide a wrapper for this system call; call it using
>>> syscall(2).
>>
>> You might mention that pthread_mutex, pthread_condvar interfaces are
>> high level wrappers for the syscall and recommended to be used for
>> normal use cases. IIRC unnamed semaphores are implemented with futexes
>> as well.
>
> If we add this, I'd rephrase it to something like that there are
> high-level programming abstractions such as the pthread_condvar
> interfaces or semaphores that are implemented using the syscall and that
> are typically a better fit for normal use cases. I'd consider only the
> condvars as something like a wrapper, or targeting a similar use case.
I added this under NOTES:
Various higher-level programming abstractions are implemented via
futexes, including POSIX threads mutexes and condition variables,
as well as POSIX semaphores.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2015-07-27 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 8:53 Michael Kerrisk (man-pages)
2015-03-28 8:56 ` Michael Kerrisk (man-pages)
2015-03-28 11:47 ` Peter Zijlstra
2015-03-28 12:03 ` Peter Zijlstra
2015-03-31 20:36 ` Davidlohr Bueso
2015-07-27 11:00 ` Michael Kerrisk (man-pages)
2015-07-27 11:10 ` Michael Kerrisk (man-pages)
2015-03-31 14:45 ` Davidlohr Bueso
2015-07-27 11:10 ` Michael Kerrisk (man-pages)
2015-07-28 3:16 ` Davidlohr Bueso
2015-07-28 7:44 ` Michael Kerrisk (man-pages)
2015-07-28 17:52 ` Davidlohr Bueso
2015-07-28 18:09 ` Michael Kerrisk (man-pages)
2015-04-14 21:40 ` Thomas Gleixner
2015-04-15 10:28 ` Torvald Riegel
2015-07-27 11:10 ` Michael Kerrisk (man-pages) [this message]
2015-04-27 20:37 ` Pavel Machek
2015-07-27 11:10 ` Michael Kerrisk (man-pages)
2015-07-28 2:52 ` Davidlohr Bueso
2015-07-28 6:39 ` Michael Kerrisk (man-pages)
2015-03-31 1:48 ` Rusty Russell
2015-07-27 11:03 ` Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55B611AF.4030600@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=anton@samba.org \
--cc=arnd@arndb.de \
--cc=bert.hubert@netherlabs.nl \
--cc=bgallmeister@gmail.com \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=jakub@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=roland@hack.frob.com \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=triegel@redhat.com \
--cc=wagi@monom.org \
--cc=xypron.glpk@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome