From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/6] change vectored block I/O API to plain iovecs
Date: Sun, 15 Mar 2009 15:36:29 +0200 [thread overview]
Message-ID: <49BD045D.6030601@redhat.com> (raw)
In-Reply-To: <49BD0080.6050709@codemonkey.ws>
Anthony Liguori wrote:
>> virtio gets its iovecs through a hacky (and incorrect, try >=4G)
>> method. IMO virtio should be fixed to use the dma api, at which
>> point it will start to use QEMUIOVector anyway,
>
> >= 4GB should work fine in virtio. It basically replicates the DMA
> API today. It doesn't handle MMIO memory though.
>
Right. I saw phys_ram_base somewhere and jumped to conclusions. Sorry
about the noise.
Still, it should use the dma api to avoid code duplication.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-15 13:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 19:27 [Qemu-devel] [PATCH 0/6] add real vectored block I/O support Christoph Hellwig
2009-03-14 19:27 ` [Qemu-devel] [PATCH 1/6] more BlockDriver C99 initializers Christoph Hellwig
2009-03-28 18:35 ` Christoph Hellwig
2009-03-14 19:28 ` [Qemu-devel] [PATCH 2/6] change vectored block I/O API to plain iovecs Christoph Hellwig
2009-03-15 12:42 ` Avi Kivity
2009-03-15 13:20 ` Anthony Liguori
2009-03-15 13:36 ` Avi Kivity [this message]
2009-03-15 14:48 ` Christoph Hellwig
2009-03-15 15:07 ` Avi Kivity
2009-03-15 16:35 ` Christoph Hellwig
2009-03-14 19:28 ` [Qemu-devel] [PATCH 3/6] virtio-blk: use generic vectored I/O APIs Christoph Hellwig
2009-03-14 19:30 ` [Qemu-devel] [PATCH 4/6] remove bdrv_aio_read/bdrv_aio_write Christoph Hellwig
2009-03-14 19:30 ` [Qemu-devel] [PATCH 5/6] push down vector linearization to posix-aio-compat.c Christoph Hellwig
2009-03-14 19:31 ` [Qemu-devel] [PATCH 6/6] experimental native preadv/pwritev support for Linux Christoph Hellwig
2009-03-15 14:36 ` Blue Swirl
2009-03-15 14:44 ` Christoph Hellwig
2009-03-15 15:03 ` Blue Swirl
2009-03-15 15:16 ` Christoph Hellwig
2009-03-16 11:38 ` Gerd Hoffmann
2009-03-16 11:53 ` Christoph Hellwig
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=49BD045D.6030601@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.