From: John Coiner <jcoiner@stanfordalumni.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [patch] Concurrent IO Support
Date: Fri, 30 Sep 2005 03:53:08 -0400 [thread overview]
Message-ID: <433CEEE4.806@stanfordalumni.org> (raw)
Folks,
Here's a patch which allows guest CPU cycles to run concurrent with IO
syscalls:
http://people.brandeis.edu/~jcoiner/qemu_idedma/qemu_dma_patch.html
It's actually two patches -- a patch which enables DMA support (the same
one posted here a few days ago) and a second patch which applies on top
of the first. The second patch is the big one, because there was a
little bit of refactoring and a few chunks of new code needed to get
concurrent IO going.
If you try this, please let me know what your experience is. This patch
makes the IDE code a little more gnarly, so it's only worth applying if
people notice the speed-up.
Under both CPU load and IO load, the patch improves the performance of
each, at least on my system. I haven't seen it make anything slower yet.
Troy and Henrik: thanks for suggesting AIO. That is probably the way to
go. This patch uses pthreads, because I was more comfortable with them.
The Linux Posix AIO stuff looked a little young. In the future, though,
it should be pretty easy to convert this implementation to AIO.
Regards,
--John
reply other threads:[~2005-09-30 8:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=433CEEE4.806@stanfordalumni.org \
--to=jcoiner@stanfordalumni.org \
--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).