From: Darren Hart <dvhltc@us.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Michael Schnell <mschnell@lumino.de>,
linux-kernel@vger.kernel.org,
Mike Frysinger <vapier.adi@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Jakub Jelinek <jakub@redhat.com>,
Thomas Chou <thomas@wytron.com.tw>
Subject: Re: implementing Futex
Date: Mon, 31 Aug 2009 09:30:10 -0700 [thread overview]
Message-ID: <4A9BFA92.2030300@us.ibm.com> (raw)
In-Reply-To: <200908141533.16714.arnd@arndb.de>
Arnd Bergmann wrote:
> On Friday 14 August 2009, Michael Schnell wrote:
>> Arnd Bergmann wrote:
>>> The man page says that the last parameter is ignored for op=FUTEX_WAKE,
>>> which is correct. The code that you were looking at however is for
>>> of=FUTEX_WAKE_OP, which is not documented as of manpages-3.22.
>>>
>>> It was added by Jakub back in 2005, but if he wrote a documentation
>>> for it, it never went into the man pages package. On a similar
>>> note, Ingo also added other futex operations that are not documented
>>> yet.
>>>
>> Thus in any documented software, the quite complex stuff in
>> "futex_atomic_op_inuser", which is provided in several different
>> "futex.h" files for all those architectures never is used ?
>
> No, my point was that futex_atomic_op_inuser is indeed used
> correctly, it's just not documented.
> See http://lwn.net/Articles/148830/ for the initial posting
>
>> Is there any viable use for this ?
>
> glibc heavily uses it for the pthreads implementation.
>
>> Would it not be appropriate either to do a documentation or to remove it ?
>
> Adding documentation, yes.
I also recently added two futex op codes which need to be added to the
man page, but they are documented in Documentation/futex-requeue-pi.txt.
Documentation/pi-futex.txt documents the FUTEX_(UN)LOCK_PI opcodes
which aren't in the man pages either.
--
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
next prev parent reply other threads:[~2009-08-31 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 15:03 implementing Futex Michael Schnell
2009-08-13 16:39 ` Arnd Bergmann
2009-08-13 17:28 ` Arnd Bergmann
2009-08-14 9:46 ` Michael Schnell
2009-08-14 11:44 ` Arnd Bergmann
2009-08-17 8:57 ` Mike Frysinger
2009-08-14 9:48 ` Michael Schnell
[not found] ` <4A8525A1.205@lumino.de>
[not found] ` <200908141128.01179.arnd@arndb.de>
2009-08-14 10:03 ` Michael Schnell
2009-08-14 10:11 ` Michael Schnell
2009-08-14 11:55 ` Michael Schnell
2009-08-14 12:38 ` Arnd Bergmann
2009-08-14 12:56 ` Michael Schnell
2009-08-14 13:33 ` Arnd Bergmann
2009-08-31 16:30 ` Darren Hart [this message]
2009-08-17 8:50 ` Michael Schnell
2009-08-17 11:53 ` [Nios2-dev] " Michael Schnell
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=4A9BFA92.2030300@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=arnd@arndb.de \
--cc=jakub@redhat.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mschnell@lumino.de \
--cc=mtk.manpages@gmail.com \
--cc=thomas@wytron.com.tw \
--cc=vapier.adi@gmail.com \
/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