From: "Michael S. Tsirkin" <mst@redhat.com>
To: Denis Plotnikov <dplotnikov@virtuozzo.com>
Cc: kwolf@redhat.com, fam@euphon.net, ehabkost@redhat.com,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com, den@virtuozzo.com
Subject: Re: [PATCH v3 0/2] virtio: make seg_max virtqueue size dependent
Date: Tue, 12 Nov 2019 06:39:15 -0500 [thread overview]
Message-ID: <20191112063838-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191112111354.26324-1-dplotnikov@virtuozzo.com>
On Tue, Nov 12, 2019 at 02:13:52PM +0300, Denis Plotnikov wrote:
> v3:
> * add property to set in machine type [MST]
> * add min queue size check [Stefan]
> * add avocado based test [Max, Stefan, Eduardo, Cleber]
>
> v2:
> * the standalone patch to make seg_max virtqueue size dependent
> * other patches are postponed
Looks good. I think it's best to apply this after the release,
so when release is out pls rebase and repost.
Thanks!
> v1:
> the initial series
>
> Denis Plotnikov (2):
> virtio: make seg_max virtqueue size dependent
> tests: add virtio-scsi and virtio-blk seg_max_adjust test
>
> hw/block/virtio-blk.c | 9 +-
> hw/core/machine.c | 3 +
> hw/scsi/vhost-scsi.c | 2 +
> hw/scsi/virtio-scsi.c | 10 +-
> include/hw/virtio/virtio-blk.h | 1 +
> include/hw/virtio/virtio-scsi.h | 1 +
> tests/acceptance/virtio_seg_max_adjust.py | 135 ++++++++++++++++++++++
> 7 files changed, 159 insertions(+), 2 deletions(-)
> create mode 100755 tests/acceptance/virtio_seg_max_adjust.py
>
> --
> 2.17.0
next prev parent reply other threads:[~2019-11-12 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 11:13 [PATCH v3 0/2] virtio: make seg_max virtqueue size dependent Denis Plotnikov
2019-11-12 11:13 ` [PATCH v3 1/2] " Denis Plotnikov
2019-11-12 11:13 ` [PATCH v3 2/2] tests: add virtio-scsi and virtio-blk seg_max_adjust test Denis Plotnikov
2019-11-12 11:39 ` Michael S. Tsirkin [this message]
2019-11-21 13:33 ` [PATCH v3 0/2] virtio: make seg_max virtqueue size dependent Stefan Hajnoczi
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=20191112063838-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=den@virtuozzo.com \
--cc=dplotnikov@virtuozzo.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).