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 v4 0/2] virtio: make seg_max virtqueue size dependent
Date: Mon, 16 Dec 2019 06:04:21 -0500 [thread overview]
Message-ID: <20191216060349-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20191216100451.28060-1-dplotnikov@virtuozzo.com>
On Mon, Dec 16, 2019 at 01:04:49PM +0300, Denis Plotnikov wrote:
> v4:
> * rebased on 4.2 [MST]
Looks good. Can I get some acks from storage guys pls?
> 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
>
> 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-12-16 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 10:04 [PATCH v4 0/2] virtio: make seg_max virtqueue size dependent Denis Plotnikov
2019-12-16 10:04 ` [PATCH v4 1/2] " Denis Plotnikov
2019-12-19 12:27 ` Michael S. Tsirkin
2019-12-16 10:04 ` [PATCH v4 2/2] tests: add virtio-scsi and virtio-blk seg_max_adjust test Denis Plotnikov
2019-12-16 11:04 ` Michael S. Tsirkin [this message]
2019-12-19 16:23 ` [PATCH v4 0/2] virtio: make seg_max virtqueue size dependent Stefan Hajnoczi
2019-12-19 16:23 ` 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=20191216060349-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 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.