From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/5] Convert vectored aio emulation to use a dedicated pool
Date: Mon, 16 Mar 2009 15:39:30 +0200 [thread overview]
Message-ID: <49BE5692.1030509@redhat.com> (raw)
In-Reply-To: <20090316133202.GB4200@lst.de>
Christoph Hellwig wrote:
> On Mon, Mar 16, 2009 at 03:11:08PM +0200, Avi Kivity wrote:
>
>> This allows us to remove a hack in the vectored aio cancellation code.
>>
>
> Note that patch my switch to the aio_readv/writev methods will get rid of
> this whole double aiocb indirection in a very natural way.
>
Right, when you don't use a synthetic aiocb, the need goes away.
We'll still have one for the block-dma-helpers, due to the need to
fragment a request when bounce resources are exhausted.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-16 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 13:11 [Qemu-devel] [PATCH 0/5] Fix aio cancellation with synthetic aiocbs Avi Kivity
2009-03-16 13:11 ` [Qemu-devel] [PATCH 1/5] Refactor aio callback allocation to use an aiocb pool Avi Kivity
2009-03-16 13:11 ` [Qemu-devel] [PATCH 2/5] Convert vectored aio emulation to use a dedicated pool Avi Kivity
2009-03-16 13:32 ` Christoph Hellwig
2009-03-16 13:39 ` Avi Kivity [this message]
2009-03-16 13:44 ` Christoph Hellwig
2009-03-16 13:11 ` [Qemu-devel] [PATCH 3/5] Implement cancellation method for dma async I/O Avi Kivity
2009-03-16 13:11 ` [Qemu-devel] [PATCH 4/5] Use vectored aiocb storage to store vector translation state Avi Kivity
2009-03-16 13:11 ` [Qemu-devel] [PATCH 5/5] Move block dma helpers aiocb to store dma state Avi Kivity
2009-03-20 18:26 ` [Qemu-devel] Re: [PATCH 0/5] Fix aio cancellation with synthetic aiocbs Anthony Liguori
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=49BE5692.1030509@redhat.com \
--to=avi@redhat.com \
--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.