From: Yongji Xie <xieyongji@bytedance.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
mreitz@redhat.com, mlureau@redhat.com, jsnow@redhat.com,
Eric Blake <eblake@redhat.com>,
Coiby.Xu@gmail.com, hreitz@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org
Subject: Re: [PATCH v5 3/8] block/export: Abstract out the logic of virtio-blk I/O process
Date: Thu, 19 May 2022 16:09:50 +0800 [thread overview]
Message-ID: <CACycT3supsS-KpX6VjiX4SyhV3wrOwPyK-0UX3vPLkbu_PdvWg@mail.gmail.com> (raw)
In-Reply-To: <YoTxEbiG3i0SZx7e@stefanha-x1.localdomain>
On Wed, May 18, 2022 at 9:14 PM Stefan Hajnoczi <stefanha@redhat.com> wrote:
>
> On Wed, May 04, 2022 at 03:40:46PM +0800, Xie Yongji wrote:
> > -static void vu_blk_req_complete(VuBlkReq *req)
> > +static void vu_blk_req_complete(VuBlkReq *req, size_t in_len)
> > {
> > VuDev *vu_dev = &req->server->vu_dev;
> >
> > - /* IO size with 1 extra status byte */
> > - vu_queue_push(vu_dev, req->vq, &req->elem, req->size + 1);
> > + vu_queue_push(vu_dev, req->vq, &req->elem, in_len);
>
> I think this silently fixes a bug: now the correct len value is
> calculated. Before the I/O buffer wasn't counted in read requests.
Yes.
> Please mention this in the commit description.
>
OK.
> > +static bool virtio_blk_sect_range_ok(BlockBackend *blk,
> > + uint64_t sector, size_t size)
> > +{
> > + uint64_t nb_sectors;
> > + uint64_t total_sectors;
> > +
> > + if (size % VIRTIO_BLK_SECTOR_SIZE) {
> > + return false;
> > + }
> > +
> > + nb_sectors = size >> VIRTIO_BLK_SECTOR_BITS;
> > +
> > + QEMU_BUILD_BUG_ON(BDRV_SECTOR_SIZE != VIRTIO_BLK_SECTOR_SIZE);
> > + if (nb_sectors > BDRV_REQUEST_MAX_SECTORS) {
> > + return false;
> > + }
> > + if ((sector << VIRTIO_BLK_SECTOR_BITS) % blk_get_guest_block_size(blk)) {
>
> Please use VirtioBlkHandler->logical_block_size instead (see below).
>
> > +int coroutine_fn virtio_blk_process_req(BlockBackend *blk, bool writable,
> > + const char *serial,
>
> I suggest defining a struct instead of passing individual arguments:
>
> typedef struct {
> BlockBackend *blk;
> const char *serial;
> uint32_t logical_block_size;
> bool writable;
> } VirtioBlkHandler;
OK, will do it in v6.
Thanks,
Yongji
next prev parent reply other threads:[~2022-05-19 8:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 7:40 [PATCH v5 0/8] Support exporting BDSs via VDUSE Xie Yongji
2022-05-04 7:40 ` [PATCH v5 1/8] block: Support passing NULL ops to blk_set_dev_ops() Xie Yongji
2022-05-18 13:22 ` Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 2/8] block-backend: Introduce blk_get_guest_block_size() Xie Yongji
2022-05-18 13:16 ` Stefan Hajnoczi
2022-05-19 8:03 ` Yongji Xie
2022-05-04 7:40 ` [PATCH v5 3/8] block/export: Abstract out the logic of virtio-blk I/O process Xie Yongji
2022-05-18 13:13 ` Stefan Hajnoczi
2022-05-19 8:09 ` Yongji Xie [this message]
2022-05-04 7:40 ` [PATCH v5 4/8] linux-headers: Add vduse.h Xie Yongji
2022-05-18 13:22 ` Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 5/8] libvduse: Add VDUSE (vDPA Device in Userspace) library Xie Yongji
2022-05-18 13:46 ` Stefan Hajnoczi
2022-05-19 8:11 ` Yongji Xie
2022-05-04 7:40 ` [PATCH v5 6/8] vduse-blk: Implement vduse-blk export Xie Yongji
2022-05-18 13:50 ` Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 7/8] vduse-blk: Add vduse-blk resize support Xie Yongji
2022-05-18 13:51 ` Stefan Hajnoczi
2022-05-04 7:40 ` [PATCH v5 8/8] libvduse: Add support for reconnecting Xie Yongji
2022-05-18 14:03 ` Stefan Hajnoczi
2022-05-19 8:25 ` Yongji Xie
2022-05-19 9:44 ` Stefan Hajnoczi
2022-05-19 10:02 ` Yongji Xie
2022-05-19 11:28 ` Stefan Hajnoczi
2022-05-13 10:03 ` [PATCH v5 0/8] Support exporting BDSs via VDUSE Michael S. Tsirkin
2022-05-17 13:02 ` Yongji Xie
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=CACycT3supsS-KpX6VjiX4SyhV3wrOwPyK-0UX3vPLkbu_PdvWg@mail.gmail.com \
--to=xieyongji@bytedance.com \
--cc=Coiby.Xu@gmail.com \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mlureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--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 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.