From: bert hubert <ahu@ds9a.nl>
To: Jakub Jelinek <jakub@redhat.com>
Cc: arnd@arndb.de, drepper@redhat.com, jamie@shareable.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
schwidefsky@de.ibm.com
Subject: Re: DOCUMENTATION Re: [PATCH] Add FUTEX_CMP_REQUEUE futex op
Date: Fri, 28 May 2004 17:39:54 +0200 [thread overview]
Message-ID: <20040528153953.GA20648@outpost.ds9a.nl> (raw)
In-Reply-To: <20040528140234.GH4736@devserv.devel.redhat.com>
On Fri, May 28, 2004 at 10:02:34AM -0400, Jakub Jelinek wrote:
> The man pages in the 2nd section document the behaviour of the userland
> wrappers (see e.g. read(2)), not what the kernel actually returns.
Ok - but in the absence of futex(2), is it perhaps better to move this page
to futex(9)? Or merge it into futex(4)?
> > Ulrich, does/will glibc provide a futex(2) function? Or should people just
> > call the syscall themselves?
>
> glibc doesn't provide a futex(2) function, so at least ATM people can use
> #include <sys/syscall.h>
If it will provide one, I'll change the page to be in line with how futex(2)
will probably work, with errno etc.
Regarding the verbiage, I need input about the use of the word 'process', as
I'm not sure if there is a generic word covering both processes and threads.
Jamie suggests 'tasks', but that is kernel lingo and of little use for
userspace developers. Suggestions?
Thanks.
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-05-28 15:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 9:38 Jakub Jelinek
2004-05-20 22:52 ` Andrew Morton
2004-05-21 6:06 ` Ulrich Drepper
2004-05-21 6:36 ` Andrew Morton
2004-05-21 7:15 ` Ulrich Drepper
2004-05-21 7:43 ` Jakub Jelinek
2004-05-22 16:58 ` Arnd Bergmann
2004-05-24 7:34 ` Jakub Jelinek
2004-05-24 8:12 ` Andrew Morton
2004-05-24 8:19 ` Jakub Jelinek
2004-05-28 13:09 ` DOCUMENTATION " bert hubert
2004-05-28 14:02 ` Jakub Jelinek
2004-05-28 15:39 ` bert hubert [this message]
2004-05-24 8:27 ` bert hubert
2004-05-24 17:34 ` Arnd Bergmann
2004-05-21 7:05 ` Ingo Molnar
2004-05-21 23:05 ` Andrew Morton
2004-05-22 10:10 ` Ingo Oeser
2004-05-23 17:33 ` Jakub Jelinek
2004-05-29 3:13 ` Rusty Russell
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=20040528153953.GA20648@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=arnd@arndb.de \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=schwidefsky@de.ibm.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
Powered by JetHome