From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] raw-posix: add Linux native AIO support
Date: Fri, 21 Aug 2009 18:35:50 +0300 [thread overview]
Message-ID: <4A8EBED6.7060105@redhat.com> (raw)
In-Reply-To: <20090821144852.GA22645@lst.de>
On 08/21/2009 05:48 PM, Christoph Hellwig wrote:
> On Fri, Aug 21, 2009 at 12:53:49PM +0300, Avi Kivity wrote:
>
>>> + * Queue size (per-device).
>>> + *
>>> + * XXX: eventually we need to communicate this to the guest and/or make it
>>> + * tunable by the guest. If we get more outstanding requests at a
>>> time
>>> + * than this we will get EAGAIN from io_submit which is communicated
>>> to
>>> + * the guest as an I/O error.
>>> + */
>>> +#define MAX_EVENTS 128
>>>
>>>
>> Or, we could queue any extra requests.
>>
> That doesn't make much sense. We'd just do an additional level of
> queueing in addition to those already optimized implementation in the
> guest and host kernels. This is really just an issue of communicating
> the limits we have and deal with it efficiently. It should be a
> relatively small add-on patch.
>
You're right, virtio and scsi already know their queue sizes, should be
easy to pass it down the stack.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-08-21 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 14:58 [Qemu-devel] [PATCH 0/2] native Linux AIO support revisited Christoph Hellwig
2009-08-20 14:58 ` [Qemu-devel] [PATCH 1/2] raw-posix: refactor AIO support Christoph Hellwig
2009-08-20 14:58 ` [Qemu-devel] [PATCH 2/2] raw-posix: add Linux native " Christoph Hellwig
2009-08-21 9:53 ` Avi Kivity
2009-08-21 14:48 ` Christoph Hellwig
2009-08-21 15:35 ` Avi Kivity [this message]
2009-08-20 19:06 ` [Qemu-devel] [PATCH 0/2] native Linux AIO support revisited Jamie Lokier
2009-08-21 7:40 ` Avi Kivity
2009-08-21 14:50 ` Christoph Hellwig
2009-08-21 15:38 ` Avi Kivity
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=4A8EBED6.7060105@redhat.com \
--to=avi@redhat.com \
--cc=hch@lst.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.