From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: den@virtuozzo.com, stefanha@redhat.com, qemu-block@nongnu.org,
mst@redhat.com
Subject: [PATCH v2 0/1] virtio: fix IO request length in virtio SCSI/block
Date: Fri, 8 Nov 2019 16:42:48 +0300 [thread overview]
Message-ID: <20191108134249.19004-1-dplotnikov@virtuozzo.com> (raw)
v2:
* the standalone patch to make seg_max virtqueue size dependent
* other patches are postponed
v1:
the initial series
Denis Plotnikov (1):
virtio: make seg_max virtqueue size dependent
hw/block/virtio-blk.c | 2 +-
hw/scsi/virtio-scsi.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.17.0
next reply other threads:[~2019-11-08 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 13:42 Denis Plotnikov [this message]
2019-11-08 13:42 ` [PATCH v2 1/1] virtio: make seg_max virtqueue size dependent Denis Plotnikov
2019-11-08 14:26 ` Michael S. Tsirkin
2019-11-11 11:19 ` Stefan Hajnoczi
2019-11-11 11:20 ` Denis Plotnikov
2019-11-08 19:43 ` [PATCH v2 0/1] virtio: fix IO request length in virtio SCSI/block no-reply
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=20191108134249.19004-1-dplotnikov@virtuozzo.com \
--to=dplotnikov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--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).