From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Davide Libenzi <davidel@xmailserver.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
linux-api@vger.kernel.org
Subject: Re: [patch/rfc] eventfd semaphore-like behavior
Date: Thu, 5 Feb 2009 12:59:07 +1300 [thread overview]
Message-ID: <cfd18e0f0902041559l4c40d9b6k704068337a00df7a@mail.gmail.com> (raw)
In-Reply-To: <20090204155514.6abbdc8f.akpm@linux-foundation.org>
On Thu, Feb 5, 2009 at 12:55 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Wed, 4 Feb 2009 15:27:45 -0800 (PST)
> Davide Libenzi <davidel@xmailserver.org> wrote:
>
>> On Wed, 4 Feb 2009, Andrew Morton wrote:
>>
>> > On Wed, 4 Feb 2009 15:18:43 -0800 (PST)
>> > Davide Libenzi <davidel@xmailserver.org> wrote:
>> >
>> > > > > Simple test here:
>> > > > >
>> > > > > http://www.xmailserver.org/eventfd-sem.c
>> > > > >
>> > > > >
>> > > > > Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
>> > > > >
>> > > > > +/*
>> > > > > + * CAREFUL: Check include/asm-generic/fcntl.h when defining
>> > > > > + * new flags, since they might collide with O_* ones. We want
>> > > > > + * to re-use O_* flags that couldn't possibly have a meaning
>> > > > > + * from eventfd, in order to leave a free define-space for
>> > > > > + * shared O_* flags.
>> > > > > + */
>> > > > > +#define EFD_SEMAPHORE (1 << 0)
>> > > > > #define EFD_CLOEXEC O_CLOEXEC
>> > > > > #define EFD_NONBLOCK O_NONBLOCK
>> > > > >
>> > > > > +#define EFD_SHARED_FCNTL_FLAGS (O_CLOEXEC | O_NONBLOCK)
>> > > > > +#define EFD_FLAGS_SET (EFD_SHARED_FCNTL_FLAGS | EFD_SEMAPHORE)
>> > > >
>> > > > How would you recommend that userspace determine whether its kernel
>> > > > supports this feature, bearing in mind that someone might backport this
>> > > > patch into arbitrarily earlier kernel versions?
>> > > >
>> > > > What should be userspace's fallback strategy if that support is not
>> > > > present?
>> > >
>> > > #ifdef EFD_SEMAPHORE, maybe?
>> >
>> > That's compile-time. People who ship binaries will probably want
>> > to find a runtime thing for back-compatibility.
>>
>> I dunno. How do they actually do when we add new flags, like the O_ ones?
>>
>
> Dunno. Probably try the syscall and see if it returned -EINVAL. Does
> that work in this case?
As youll have seen by now, Ulrich and I noted that it works.
> If so, it would be sensible to mention this in
> the description somewhere as the approved probing method and to
> maintain it.
I'll add something to the man page, as this patch progresses.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2009-02-04 23:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 22:58 Davide Libenzi
2009-02-04 23:05 ` Andrew Morton
2009-02-04 23:18 ` Davide Libenzi
2009-02-04 23:24 ` Andrew Morton
2009-02-04 23:27 ` Davide Libenzi
2009-02-04 23:48 ` Michael Kerrisk
2009-02-04 23:55 ` Andrew Morton
2009-02-04 23:59 ` Michael Kerrisk [this message]
2009-02-05 0:02 ` Davide Libenzi
2010-08-30 5:21 ` Michael Kerrisk
2010-08-30 5:24 ` Michael Kerrisk
2010-08-30 14:22 ` Davide Libenzi
2009-02-05 0:18 ` Andrew Morton
2009-02-05 0:25 ` Davide Libenzi
2009-02-05 0:34 ` Andrew Morton
2009-02-05 0:26 ` Michael Kerrisk
2009-02-04 23:45 ` Ulrich Drepper
2009-02-04 23:49 ` Michael Kerrisk
2009-02-09 7:45 ` Michael Kerrisk
2009-02-09 17:39 ` Davide Libenzi
[not found] <499E527B.2030702@fastmq.com>
2009-02-20 7:00 ` Martin Sustrik
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=cfd18e0f0902041559l4c40d9b6k704068337a00df7a@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®