From: Anthony Liguori <aliguori@us.ibm.com>
To: Marcelo Tosatti <marcelo@kvack.org>,
Avi Kivity <avi@qumranet.com>,
kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: [RFC] Multiple QEMU AIO implementations
Date: Wed, 16 Apr 2008 16:36:42 -0500 [thread overview]
Message-ID: <4806716A.70504@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
This isn't fully cooked yet, but pretty close. The basic idea is to
make the aio usage in block-raw go to a set of function pointers and
allow multiple simultaneous AIO implementations.
I converted the posix-aio support to this, and also introduced a "unix"
aio which just uses O_NONBLOCK and select(). The later only supports 1
simultaneous request per-fd but currently posix-aio is limited to that
too. At least with my QEMU testing, the unix aio implementation
outperforms posix-aio by a factor of 2.
And it uses no signals...
I'm inclined to suggest that we use signalfd with posix-aio, and for
older guests, just fall back to unix aio. We can also introduce a
linux-aio and use that when possible.
Regards,
Anthony Liguori
[-- Attachment #2: qemu-block-aio-unix.patch --]
[-- Type: application/mbox, Size: 27260 bytes --]
[-- Attachment #3: Type: text/plain, Size: 320 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
[-- Attachment #4: Type: text/plain, Size: 158 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next reply other threads:[~2008-04-16 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 21:36 Anthony Liguori [this message]
2008-04-16 23:52 ` [RFC] Multiple QEMU AIO implementations Marcelo Tosatti
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=4806716A.70504@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=marcelo@kvack.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