From: "Sven Köhler" <skoehler@upb.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: high CPU load / async IO?
Date: Tue, 25 Jul 2006 20:15:40 +0200 [thread overview]
Message-ID: <ea5n4k$os4$1@sea.gmane.org> (raw)
In-Reply-To: <pan.2006.07.25.14.55.14.791741@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
>>> IDE only supports one outstanding request, so having a thread that runs
>>> the synchronous block routines appears reasonable. However, SATA and SCSI
>>> both support multiple outstanding requests. The extension to the existing
>>> patch would be simple--increase the number of threads.
>> ???
>>
>> Wasn't there another variant using the async-I/O support of the Host OS
>> and thereby supporting a larger number of outstanding requests?
>
> Not that I know of. Do you have a pointer?
Hmm, perhaps i only heard people talking about it ...
But if i find anything, i post the link.
>>> So the current thread-based async dma patch is really just the wrong long
>>> term solution. A more long term solution is likely in the works. It
>>> requires quite a bit of code modification though.
>>
>> I see. So in other words:
>>
>> don't ask for simple async I/O now. The more complex and flexible
>> sollution will follow soon.
>
> Yes, hopefully really soon.
So i will wait patiently :-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2006-07-25 18:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 22:47 [Qemu-devel] high CPU load / async IO? Sven Köhler
2006-07-24 18:46 ` [Qemu-devel] " Anthony Liguori
2006-07-24 22:51 ` Sven Köhler
2006-07-25 14:55 ` Anthony Liguori
2006-07-25 18:15 ` Sven Köhler [this message]
2006-07-25 19:43 ` Jens Axboe
2006-07-25 20:37 ` Fabrice Bellard
2006-07-26 7:45 ` Jens Axboe
2006-07-26 12:21 ` Paul Brook
2006-07-26 12:23 ` Jens Axboe
2006-07-26 12:27 ` Paul Brook
2006-07-26 12:46 ` Jens Axboe
2006-07-26 14:14 ` Sven Köhler
2006-07-26 17:54 ` Jens Axboe
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='ea5n4k$os4$1@sea.gmane.org' \
--to=skoehler@upb.de \
--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).