From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org
Subject: Re: [PATCH 1/1] virtio-blk-ccw: tweak the default for num_queues
Date: Mon, 9 Nov 2020 17:06:16 +0100 [thread overview]
Message-ID: <20201109170616.6875f610.cohuck@redhat.com> (raw)
In-Reply-To: <20201109154831.20779-1-pasic@linux.ibm.com>
On Mon, 9 Nov 2020 16:48:31 +0100
Halil Pasic <pasic@linux.ibm.com> wrote:
> Currently the default value of num_queues is effectively 1 for
> virtio-blk-ccw. Recently 9445e1e15e ("virtio-blk-pci: default num_queues
> to -smp N") changed the default for pci to the number of vcpus, citing
> interrupt better locality and better performance as a rationale.
>
> While virtio-blk-ccw does not yet benefit from better interrupt
> locality, measurements have shown that for secure VMs multiqueue does
> help with performance. Since the bounce buffering happens with the queue
> lock held (in the guest) this is hardly a surprise.
>
> As for non-secure VMs the extra queues shouldn't hurt too much.
>
> Suggested-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Signed-off-by: Halil Pasic <pasic@linux.ibm.com>
> ---
>
> We would prefer to land this for 5.2. If we do then commit 9445e1e15e
> ("virtio-blk-pci: default num_queues to -smp N") took care of all the
> necessary compat handling.
>
> If that's not possible, I will send a version that does the necessary
> compat handling.
I think we can still get this into 5.2, and that would indeed be less
hassle.
> ---
> hw/s390x/virtio-ccw-blk.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/hw/s390x/virtio-ccw-blk.c b/hw/s390x/virtio-ccw-blk.c
> index 2294ce1ce4..7296140dde 100644
> --- a/hw/s390x/virtio-ccw-blk.c
> +++ b/hw/s390x/virtio-ccw-blk.c
> @@ -10,6 +10,7 @@
> */
>
> #include "qemu/osdep.h"
> +#include "hw/boards.h"
> #include "hw/qdev-properties.h"
> #include "hw/virtio/virtio.h"
> #include "qapi/error.h"
> @@ -20,6 +21,11 @@ static void virtio_ccw_blk_realize(VirtioCcwDevice *ccw_dev, Error **errp)
> {
> VirtIOBlkCcw *dev = VIRTIO_BLK_CCW(ccw_dev);
> DeviceState *vdev = DEVICE(&dev->vdev);
> + VirtIOBlkConf *conf = &dev->vdev.conf;
> +
> + if (conf->num_queues == VIRTIO_BLK_AUTO_NUM_QUEUES) {
> + conf->num_queues = MIN(4, current_machine->smp.cpus);
> + }
I would like to have a comment explaining the numbers here, however.
virtio-pci has a pretty good explanation (use 1:1 for vqs:vcpus if
possible, apply some other capping). 4 seems to be a bit arbitrary
without explanation, although I'm sure you did some measurements :)
Do we also want something similar for virtio-scsi (and vhost-scsi)?
>
> qdev_realize(vdev, BUS(&ccw_dev->bus), errp);
> }
>
> base-commit: 2a190a7256a3e0563b29ffd67e0164097b4a6dac
next prev parent reply other threads:[~2020-11-09 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 15:48 [PATCH 1/1] virtio-blk-ccw: tweak the default for num_queues Halil Pasic
2020-11-09 15:53 ` Christian Borntraeger
2020-11-09 16:06 ` Cornelia Huck [this message]
2020-11-09 18:53 ` Halil Pasic
2020-11-10 8:47 ` Christian Borntraeger
2020-11-10 10:15 ` Cornelia Huck
2020-11-10 10:40 ` Halil Pasic
2020-11-10 13:18 ` Christian Borntraeger
2020-12-15 8:26 ` Cornelia Huck
2020-12-15 11:33 ` Halil Pasic
2020-12-15 17:27 ` Cornelia Huck
2020-11-10 14:16 ` Michael Mueller
2020-11-11 12:26 ` Michael Mueller
2020-11-11 12:38 ` Cornelia Huck
2020-11-11 12:49 ` Michael Mueller
2020-11-12 13:31 ` Halil Pasic
2020-11-11 15:16 ` Halil Pasic
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=20201109170616.6875f610.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@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.