qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 0/4] Block DMA helpers (v2)
Date: Sun, 08 Feb 2009 13:04:40 -0600	[thread overview]
Message-ID: <498F2CC8.6090607@us.ibm.com> (raw)
In-Reply-To: <498F1EA1.8060803@redhat.com>

Avi Kivity wrote:
> We could replace
>
>    struct iovec in_sg[VIRTQUEUE_MAX_SIZE];
>    struct iovec out_sg[VIRTQUEUE_MAX_SIZE];
>
> by QEMUSGList, which would be a minor improvement, but I thought 
> things were very different for some reason.

I'm not sure that it's just a minor improvement.  To maintain this 
interface, we have to map the full request.  If we exposed QEMUSGLists, 
then each device could choose the mapping policy.  Since there's no good 
reason to use virtio to DMA MMIO memory, I'm unsure which is the best 
approach.

> An example would be how the code is structured now (as opposed to how 
> I thought it was structured).

Okay, I was certain I was missing something obvious :-)

Regards,

Anthony Liguori

      reply	other threads:[~2009-02-08 19:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05  9:33 [Qemu-devel] [PATCH 0/4] Block DMA helpers (v2) Avi Kivity
2009-02-05  9:33 ` [Qemu-devel] [PATCH 1/4] Add a scatter-gather list type and accessors Avi Kivity
2009-02-05  9:33 ` [Qemu-devel] [PATCH 2/4] Add qemu_iovec_reset() Avi Kivity
2009-02-05  9:33 ` [Qemu-devel] [PATCH 3/4] Introduce block dma helpers Avi Kivity
2009-02-05  9:33 ` [Qemu-devel] [PATCH 4/4] Convert IDE to use new " Avi Kivity
2009-02-05 21:25 ` [Qemu-devel] Re: [PATCH 0/4] Block DMA helpers (v2) Anthony Liguori
2009-02-06  8:52   ` Avi Kivity
2009-02-06 15:12     ` Anthony Liguori
2009-02-07 21:16       ` Avi Kivity
2009-02-07 23:50         ` Anthony Liguori
2009-02-08  9:30           ` Avi Kivity
2009-02-08 17:59             ` Anthony Liguori
2009-02-08 18:04               ` Avi Kivity
2009-02-08 19:04                 ` Anthony Liguori [this message]

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=498F2CC8.6090607@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=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 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).