From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: qemu (cvs-version) performance?
Date: Sat, 11 Mar 2006 18:01:15 -0500 [thread overview]
Message-ID: <20060311230115.GA30203@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <duvjc7$d7$1@sea.gmane.org>
On Sat, Mar 11, 2006 at 11:35:48PM +0100, Sven K?hler wrote:
> I have seen thoughts about asynchronous IO for qemu. I thought that they
> would have been integrated along with the DMA-patches already.
>
> I would really see how qemu performs with asynch IO enabled. Are there
> any patches out there?
>
There was one that used threads to do IO asychonrously, but iiuc the final
patches (which will use posix? async io) are still being worked on..
You can find the patches in the mailing list archives.
>
> Greetings
> Sven
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2006-03-11 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 3:34 [Qemu-devel] qemu (cvs-version) performance? Sven Köhler
2006-03-11 22:25 ` Paul Brook
2006-03-11 22:35 ` [Qemu-devel] " Sven Köhler
2006-03-11 22:58 ` Sven Köhler
2006-03-11 23:01 ` Jim C. Brown [this message]
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=20060311230115.GA30203@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).