From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
rusty@rustcorp.com.au, qemu-devel@nongnu.org, khoa@us.ibm.com,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
asias@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 7/8] dataplane: add virtio-blk data plane code
Date: Tue, 20 Nov 2012 14:54:05 +0100 [thread overview]
Message-ID: <20121120135404.GB28489@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20121120130453.GA3448@redhat.com>
On Tue, Nov 20, 2012 at 03:04:53PM +0200, Michael S. Tsirkin wrote:
> On Tue, Nov 20, 2012 at 01:31:51PM +0100, Stefan Hajnoczi wrote:
> > +static void process_request(IOQueue *ioq, struct iovec iov[],
> > + unsigned int out_num, unsigned int in_num,
> > + unsigned int head)
> > +{
> > + /* Virtio block requests look like this: */
> > + struct virtio_blk_outhdr *outhdr; /* iov[0] */
> > + /* data[] ... */
> > + struct virtio_blk_inhdr *inhdr; /* iov[out_num + in_num - 1] */
> > +
> > + if (unlikely(out_num == 0 || in_num == 0 ||
> > + iov[0].iov_len != sizeof *outhdr ||
> > + iov[out_num + in_num - 1].iov_len != sizeof *inhdr)) {
> > + fprintf(stderr, "virtio-blk invalid request\n");
> > + exit(1);
> > + }
> > +
> > + outhdr = iov[0].iov_base;
> > + inhdr = iov[out_num + in_num - 1].iov_base;
> > +
>
> Rusty is trying to get rid of hard-coded layout assumptions,
> let's not add any more if we can help it.
Will try to abstract the iov arrays in the next version. Still not a
fan of doing this because it complicates the code for little gain.
Stefan
next prev parent reply other threads:[~2012-11-20 13:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 12:31 [Qemu-devel] [PATCH v2 0/8] virtio: virtio-blk data plane Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 1/8] raw-posix: add raw_get_aio_fd() for virtio-blk-data-plane Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 2/8] configure: add CONFIG_VIRTIO_BLK_DATA_PLANE Stefan Hajnoczi
2012-11-21 18:17 ` mdroth
2012-11-21 18:29 ` Stefan Hajnoczi
2012-11-21 18:45 ` mdroth
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 3/8] dataplane: add host memory mapping code Stefan Hajnoczi
2012-11-20 18:24 ` Don Koch
2012-11-21 7:59 ` Stefan Hajnoczi
2012-11-26 15:31 ` Don Koch
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 4/8] dataplane: add virtqueue vring code Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 5/8] dataplane: add event loop Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 6/8] dataplane: add Linux AIO request queue Stefan Hajnoczi
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 7/8] dataplane: add virtio-blk data plane code Stefan Hajnoczi
2012-11-20 13:04 ` Michael S. Tsirkin
2012-11-20 13:54 ` Stefan Hajnoczi [this message]
2012-11-20 12:31 ` [Qemu-devel] [PATCH v2 8/8] virtio-blk: add x-data-plane=on|off performance feature Stefan Hajnoczi
2012-11-20 12:37 ` Daniel P. Berrange
2012-11-20 12:53 ` Kevin Wolf
2012-11-20 13:50 ` Stefan Hajnoczi
2012-11-20 14:34 ` Daniel P. Berrange
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=20121120135404.GB28489@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=asias@redhat.com \
--cc=khoa@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=stefanha@redhat.com \
/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).