From: Benjamin LaHaise <bcrl@kvack.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Zach Brown <zach.brown@oracle.com>
Subject: Re: [patch 13/13] signalfd/timerfd/asyncfd v5 - KAIO asyncfd support (example/maybe-broken) ...
Date: Wed, 14 Mar 2007 20:02:12 -0400 [thread overview]
Message-ID: <20070315000212.GD1246@kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0703141638570.4982@alien.or.mcafeemobile.com>
On Wed, Mar 14, 2007 at 04:41:58PM -0700, Davide Libenzi wrote:
> Yeah, of course. I do not plan revolutions. Just asking if it's a possible
> thing to do. I can mlock the userspace ring, if imposing that burden over
> aio_complete() is seen as too heavy.
I'm not sure I follow what you're doing -- why isn't asyncfd merely calling
io_getevents() instead of reinventing everything the ringbuffer does? The
aio ringbuffer is already locked in memory. Fwiw, the aio ringbuffer was
originally wired up to a file descriptor, but that gave way to the actual
syscall in order to enforce proper typechecking and typical usage scenarios
with timeouts.
Also, there have been patches floating around for aio_poll and a way to get
epoll wakeups into the aio event queue. They deserve serious consideration
if this asyncfd seems necessary.
-ben
--
"Time is of no importance, Mr. President, only life is important."
Don't Email: <zyntrop@kvack.org>.
next prev parent reply other threads:[~2007-03-15 0:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 22:19 Davide Libenzi
2007-03-14 23:19 ` Benjamin LaHaise
2007-03-14 23:24 ` Davide Libenzi
2007-03-14 23:42 ` Benjamin LaHaise
2007-03-14 23:41 ` Davide Libenzi
2007-03-14 23:49 ` Davide Libenzi
2007-03-15 0:02 ` Benjamin LaHaise [this message]
2007-03-15 0:10 ` Davide Libenzi
2007-03-15 0:27 ` Davide Libenzi
2007-03-15 0:15 ` Linus Torvalds
2007-03-15 0:15 ` 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=20070315000212.GD1246@kvack.org \
--to=bcrl@kvack.org \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suparna@in.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=zach.brown@oracle.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
all inboxes | Powered by JetHome®