From: Davide Libenzi <davidel@xmailserver.org>
To: mtk.manpages@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch/rfc] eventfd semaphore-like behavior
Date: Mon, 9 Feb 2009 09:39:52 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.1.10.0902090932320.8084@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <cfd18e0f0902082345o7e36f4deo27fc3466aba66dad@mail.gmail.com>
On Mon, 9 Feb 2009, Michael Kerrisk wrote:
> On Thu, Feb 5, 2009 at 11:58 AM, Davide Libenzi <davidel@xmailserver.org> wrote:
> > People started using eventfd in scnarios where before where using pipes.
> > Many of them use eventfds in a semaphore-like way, like they were before
> > with pipes. The problem with eventfd is that a read() on the fd returns
> > and wipes the whole counter, making the use of it as semaphore a little
> > bit more cumbersome. You can do a read() followed by a write() of
> > COUNTER-1, but IMO it's pretty easy and cheap to make this work w/out
> > extra steps. This patch introduces a new eventfd flag that tells eventfd
> > to only dequeue 1 from the counter, allowing simple read/write to make it
> > behave like a semaphore.
> > Simple test here:
> >
> > http://www.xmailserver.org/eventfd-sem.c
> >
> >
> > Signed-off-by: Davide Libenzi <davidel@xmailserver.org>
>
> Tested-by: Michael Kerrisk <mtk.manpages@gmail.com>
>
> Applied this patch against 2.6.29-rc3, and it works as I would expect.
>
>
> A question or two.... This change is rather specific to a single use
> case, so I wonder
>
> a) Are there use cases that require the ability to read an arbitrary
> number of units off the eventfd -- i.e., read N units off the eventfd,
> rather than just 1?
Not that I can think of.
> b) Is it desirable to be able to toggle the EFD_SEMAPHORE behavior on
> and off for an eventfd?
This I'd say no. A synchronization entity in all decently sane sw design
I've ever seen, remains the same in behaviour and it is never changed
runtime to behave in different ways.
> It's difficult to see how these use cases could be accommodated in the
> current API, but I just thought it worth raising the ideas.
Since read/write semantics cannot be changed (besides, like the semaphore
change, for the amount of "data" dequeued), deeper changes to the
interface will have to go via ioctl(). But I don't see any reason to go
that way ATM.
- Davide
next prev parent reply other threads:[~2009-02-09 17:40 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
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 [this message]
[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=alpine.DEB.1.10.0902090932320.8084@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.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®