From: Avi Kivity <avi@redhat.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
kvm@vger.kernel.org, Gregory Haskins <ghaskins@novell.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: [patch] eventfd - revised interface and cleanups
Date: Tue, 23 Jun 2009 20:03:13 +0300 [thread overview]
Message-ID: <4A410AD1.8080304@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0906230936280.17001@makko.or.mcafeemobile.com>
On 06/23/2009 07:47 PM, Davide Libenzi wrote:
> The following patch changes the eventfd interface to de-couple the eventfd
> memory context, from the file pointer instance.
> Without such change, there is no clean way to racely free handle the
> POLLHUP event sent when the last instance of the file* goes away.
> Also, now the internal eventfd APIs are using the eventfd context instead
> of the file*.
> Another cleanup this patch does, is making AIO select EVENTFD, instead of
> adding a bunch of empty function stubs inside eventfd.h.
>
> Andrew, this better go via Avi and the KVM tree, since they have patches
> that will be based on the new interface.
>
The kvm patches will only be ready for 2.6.32. Can this go in 2.6.31
now, and we'll meet in 10 weeks?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-23 17:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 16:47 [patch] eventfd - revised interface and cleanups Davide Libenzi
2009-06-23 16:59 ` Randy Dunlap
2009-06-23 17:04 ` Davide Libenzi
2009-06-23 17:03 ` Avi Kivity [this message]
2009-06-23 17:04 ` Davide Libenzi
2009-06-23 17:51 ` Gregory Haskins
2009-06-23 17:51 ` Davide Libenzi
2009-06-23 19:25 ` [patch] eventfd - revised interface and cleanups (2nd rev) Davide Libenzi
2009-06-23 19:48 ` Andrew Morton
2009-06-23 19:49 ` Davide Libenzi
2009-06-23 20:12 ` Andrew Morton
2009-06-23 20:59 ` Davide Libenzi
2009-06-23 21:25 ` Andrew Morton
2009-06-23 21:25 ` Davide Libenzi
2009-06-23 21:44 ` Andrew Morton
2009-06-23 22:49 ` Davide Libenzi
2009-06-23 23:18 ` Andrew Morton
2009-06-24 22:47 ` Davide Libenzi
2009-06-24 23:12 ` Andrew Morton
2009-06-24 23:52 ` Davide Libenzi
2009-06-25 0:33 ` Andrew Morton
2009-06-23 20:18 ` Andrew Morton
2009-06-23 21:03 ` Davide Libenzi
2009-06-23 21:29 ` Andrew Morton
2009-06-23 21:28 ` Davide Libenzi
2009-06-23 21:34 ` Davide Libenzi
2009-06-23 21:46 ` Andrew Morton
2009-06-23 21:48 ` Davide Libenzi
2009-06-23 22:07 ` Andrew Morton
2009-06-23 22:46 ` [patch] eventfd - revised interface and cleanups (3rd rev) Davide Libenzi
2009-06-24 23:57 ` [patch] eventfd - revised interface and cleanups (4th rev) Davide Libenzi
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=4A410AD1.8080304@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=davidel@xmailserver.org \
--cc=ghaskins@novell.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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