From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
slp@redhat.com, cohuck@redhat.com, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [PATCH RESEND v3 0/4] virtio-pci: enable blk and scsi multi-queue by default
Date: Sun, 29 Mar 2020 09:49:30 -0400 [thread overview]
Message-ID: <20200329094907-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200320103041.129527-1-stefanha@redhat.com>
On Fri, Mar 20, 2020 at 10:30:37AM +0000, Stefan Hajnoczi wrote:
> v3:
> * Add new performance results that demonstrate the scalability
> * Mention that this is PCI-specific [Cornelia]
> v2:
> * Let the virtio-DEVICE-pci device select num-queues because the optimal
> multi-queue configuration may differ between virtio-pci, virtio-mmio, and
> virtio-ccw [Cornelia]
I'd like to queue it for merge after the release. If possible
please ping me after the release to help make sure it didn't get
dropped.
Thanks!
> Enabling multi-queue on virtio-pci storage devices improves performance on SMP
> guests because the completion interrupt is handled on the vCPU that submitted
> the I/O request. This avoids IPIs inside the guest.
>
> Note that performance is unchanged in these cases:
> 1. Uniprocessor guests. They don't have IPIs.
> 2. Application threads might be scheduled on the sole vCPU that handles
> completion interrupts purely by chance. (This is one reason why benchmark
> results can vary noticably between runs.)
> 3. Users may bind the application to the vCPU that handles completion
> interrupts.
>
> Set the number of queues to the number of vCPUs by default on virtio-blk and
> virtio-scsi PCI devices. Older machine types continue to default to 1 queue
> for live migration compatibility.
>
> Random read performance:
> IOPS
> q=1 78k
> q=32 104k +33%
>
> Boot time:
> Duration
> q=1 51s
> q=32 1m41s +98%
>
> Guest configuration: 32 vCPUs, 101 virtio-blk-pci disks
>
> Previously measured results on a 4 vCPU guest were also positive but showed a
> smaller 1-4% performance improvement. They are no longer valid because
> significant event loop optimizations have been merged.
>
> Stefan Hajnoczi (4):
> virtio-scsi: introduce a constant for fixed virtqueues
> virtio-scsi: default num_queues to -smp N
> virtio-blk: default num_queues to -smp N
> vhost-user-blk: default num_queues to -smp N
>
> hw/block/vhost-user-blk.c | 6 +++++-
> hw/block/virtio-blk.c | 6 +++++-
> hw/core/machine.c | 5 +++++
> hw/scsi/vhost-scsi.c | 3 ++-
> hw/scsi/vhost-user-scsi.c | 5 +++--
> hw/scsi/virtio-scsi.c | 13 +++++++++----
> hw/virtio/vhost-scsi-pci.c | 10 ++++++++--
> hw/virtio/vhost-user-blk-pci.c | 6 ++++++
> hw/virtio/vhost-user-scsi-pci.c | 10 ++++++++--
> hw/virtio/virtio-blk-pci.c | 9 ++++++++-
> hw/virtio/virtio-scsi-pci.c | 10 ++++++++--
> include/hw/virtio/vhost-user-blk.h | 2 ++
> include/hw/virtio/virtio-blk.h | 2 ++
> include/hw/virtio/virtio-scsi.h | 5 +++++
> 14 files changed, 76 insertions(+), 16 deletions(-)
>
> --
> 2.24.1
>
next prev parent reply other threads:[~2020-03-29 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 10:30 [PATCH RESEND v3 0/4] virtio-pci: enable blk and scsi multi-queue by default Stefan Hajnoczi
2020-03-20 10:30 ` [PATCH RESEND v3 1/4] virtio-scsi: introduce a constant for fixed virtqueues Stefan Hajnoczi
2020-03-20 10:30 ` [PATCH RESEND v3 2/4] virtio-scsi: default num_queues to -smp N Stefan Hajnoczi
2020-03-20 10:58 ` Cornelia Huck
2020-03-20 10:30 ` [PATCH RESEND v3 3/4] virtio-blk: " Stefan Hajnoczi
2020-03-20 10:30 ` [PATCH RESEND v3 4/4] vhost-user-blk: " Stefan Hajnoczi
2020-03-29 13:49 ` Michael S. Tsirkin [this message]
2020-03-30 14:35 ` [PATCH RESEND v3 0/4] virtio-pci: enable blk and scsi multi-queue by default Pankaj Gupta
2020-05-04 14:11 ` Michael S. Tsirkin
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=20200329094907-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=slp@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.