From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: famz@redhat.com, hare@suse.de, vrozenfe@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/4] scsi-disk: introduce dma_readv and dma_writev
Date: Thu, 19 May 2016 09:11:17 -0600 [thread overview]
Message-ID: <573DD795.4090201@redhat.com> (raw)
In-Reply-To: <1462966873-30473-4-git-send-email-pbonzini@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]
On 05/11/2016 05:41 AM, Paolo Bonzini wrote:
> These are replacements for blk_aio_readv and blk_aio_writev that allow
> customization of the data path. They reuse the DMA helpers' DMAIOFunc
> callback type, so that the same function can be used in either the
> QEMUSGList or the bounce-buffered case.
>
> This customization will be needed in the next patch to do zero-copy
> SG_IO on scsi-block.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> hw/scsi/scsi-disk.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 56 insertions(+), 8 deletions(-)
>
> @@ -339,14 +354,16 @@ static void scsi_do_read(SCSIDiskReq *r, int ret)
> if (r->req.sg) {
> dma_acct_start(s->qdev.conf.blk, &r->acct, r->req.sg, BLOCK_ACCT_READ);
> r->req.resid -= r->req.sg->size;
> - r->req.aiocb = dma_blk_read(s->qdev.conf.blk, r->req.sg, r->sector,
> - scsi_dma_complete, r);
> + r->req.aiocb = dma_blk_io(blk_get_aio_context(s->qdev.conf.blk),
> + r->req.sg, r->sector,
> + sdc->dma_readv, r, scsi_dma_complete, r,
> + DMA_DIRECTION_FROM_DEVICE);
Is it worth considering byte-based rather than sector-based interfaces,
as part of this series?
> +static
> +BlockAIOCB *scsi_dma_readv(int64_t sector_num,
> + QEMUIOVector *iov, int nb_sectors,
> + BlockCompletionFunc *cb, void *cb_opaque,
> + void *opaque)
> +{
> + SCSIDiskReq *r = opaque;
> + SCSIDiskState *s = DO_UPCAST(SCSIDiskState, qdev, r->req.dev);
> + return blk_aio_readv(s->qdev.conf.blk, sector_num, iov, nb_sectors,
> + cb, cb_opaque);
> +}
Especially since commit 7b1deac killed blk_aio_readv() in favor of
byte-based blk_aio_preadv().
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-05-19 15:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 11:41 [Qemu-devel] [PATCH 0/4] scsi-block: receive the right SCSI status on reads and writes Paolo Bonzini
2016-05-11 11:41 ` [Qemu-devel] [PATCH 1/4] scsi-disk: introduce a common base class Paolo Bonzini
2016-05-11 11:41 ` [Qemu-devel] [PATCH 2/4] dma-helpers: change BlockBackend to opaque value in DMAIOFunc Paolo Bonzini
2016-05-17 2:40 ` Fam Zheng
2016-05-11 11:41 ` [Qemu-devel] [PATCH 3/4] scsi-disk: introduce dma_readv and dma_writev Paolo Bonzini
2016-05-19 15:11 ` Eric Blake [this message]
2016-05-19 15:13 ` Paolo Bonzini
2016-05-11 11:41 ` [Qemu-devel] [PATCH 4/4] scsi-block: always use SG_IO Paolo Bonzini
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=573DD795.4090201@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=hare@suse.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vrozenfe@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).