From: Denis Plotnikov <dplotnikov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, vsementsov@virtuozzo.com,
ehabkost@redhat.com, qemu-block@nongnu.org, mst@redhat.com,
stefanha@redhat.com, mreitz@redhat.com, pbonzini@redhat.com,
den@virtuozzo.com
Subject: [PATCH v1 0/4] Increase default virtqueue size to improve performance
Date: Wed, 29 Jan 2020 17:06:58 +0300 [thread overview]
Message-ID: <20200129140702.5411-1-dplotnikov@virtuozzo.com> (raw)
The goal is to increase the performance of the block layer on
1M reads/writes up to 4% by reducing the amount of requests issued by a guest
using virtio-scsi or virtio-blk devices.
Original problem description:
https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg03721.html
Denis Plotnikov (4):
virtio: introduce VIRTQUEUE_DEFUALT_SIZE instead of hardcoded
constants
virtio: increase virtuqueue size for virtio-scsi and virtio-blk
tests: add virtuqueue size checking to virtio_seg_max_adjust test
tests: rename virtio_seg_max_adjust to virtio_check_params
hw/block/virtio-blk.c | 6 ++--
hw/core/machine.c | 3 ++
hw/scsi/virtio-scsi.c | 5 +--
include/hw/virtio/virtio.h | 1 +
...g_max_adjust.py => virtio_check_params.py} | 33 ++++++++++++-------
5 files changed, 32 insertions(+), 16 deletions(-)
rename tests/acceptance/{virtio_seg_max_adjust.py => virtio_check_params.py} (79%)
--
2.17.0
next reply other threads:[~2020-01-29 14:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 14:06 Denis Plotnikov [this message]
2020-01-29 14:06 ` [PATCH v1 1/4] virtio: introduce VIRTQUEUE_DEFUALT_SIZE instead of hardcoded constants Denis Plotnikov
2020-01-29 17:02 ` Philippe Mathieu-Daudé
2020-01-29 17:55 ` Cornelia Huck
2020-01-30 14:56 ` Stefan Hajnoczi
2020-02-03 12:15 ` Denis Plotnikov
2020-01-30 13:38 ` Michael S. Tsirkin
2020-02-03 12:17 ` Denis Plotnikov
2020-02-03 12:51 ` Michael S. Tsirkin
2020-02-03 12:56 ` Denis Plotnikov
2020-01-29 14:07 ` [PATCH v1 2/4] virtio: increase virtuqueue size for virtio-scsi and virtio-blk Denis Plotnikov
2020-01-30 13:40 ` Michael S. Tsirkin
2020-02-03 12:18 ` Denis Plotnikov
2020-01-30 14:58 ` Stefan Hajnoczi
2020-02-04 9:59 ` Denis Plotnikov
2020-02-05 11:19 ` Stefan Hajnoczi
2020-02-07 8:48 ` Denis Plotnikov
2020-02-07 16:13 ` Stefan Hajnoczi
2020-02-09 7:49 ` Michael S. Tsirkin
2020-02-10 15:34 ` Denis Plotnikov
2020-02-11 10:32 ` Michael S. Tsirkin
2020-02-10 17:06 ` Stefan Hajnoczi
2021-09-08 13:17 ` Stefano Garzarella
2021-09-08 13:22 ` Stefano Garzarella
2021-09-08 15:20 ` Denis Plotnikov
2021-09-09 8:28 ` Stefano Garzarella
2021-09-09 11:26 ` Denis Plotnikov
2020-01-29 14:07 ` [PATCH v1 3/4] tests: add virtuqueue size checking to virtio_seg_max_adjust test Denis Plotnikov
2020-01-30 13:42 ` Michael S. Tsirkin
2020-02-03 12:21 ` Denis Plotnikov
2020-01-29 14:07 ` [PATCH v1 4/4] tests: rename virtio_seg_max_adjust to virtio_check_params Denis Plotnikov
2021-09-08 15:45 ` Philippe Mathieu-Daudé
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=20200129140702.5411-1-dplotnikov@virtuozzo.com \
--to=dplotnikov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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).