From: Michael Mueller <mimu@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>, Cornelia Huck <cohuck@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
David Hildenbrand <david@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: Tue, 10 Nov 2020 15:16:49 +0100 [thread overview]
Message-ID: <4a3d24e0-399f-f509-9a5c-c66c57b2d28a@linux.ibm.com> (raw)
In-Reply-To: <20201109195303.459f6fba.pasic@linux.ibm.com>
On 09.11.20 19:53, Halil Pasic wrote:
> On Mon, 9 Nov 2020 17:06:16 +0100
> Cornelia Huck <cohuck@redhat.com> wrote:
>
>>> @@ -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 :)
>
> Frankly, I don't have any measurements yet. For the secure case,
> I think Mimu has assessed the impact of multiqueue, hence adding Mimu to
> the cc list. @Mimu can you help us out.
>
> Regarding the normal non-protected VMs I'm in a middle of producing some
> measurement data. This was admittedly a bit rushed because of where we
> are in the cycle. Sorry to disappoint you.
I'm talking with the perf team tomorrow. They have done some
measurements with multiqueue for PV guests and I asked for a comparison
to non PV guests as well.
Michael
>
> The number 4 was suggested by Christian, maybe Christian does have some
> readily available measurement data for the normal VM case. @Christian:
> can you help me out?
>
> Regards,
> Halil
>
--
Mit freundlichen Grüßen / Kind regards
Michael Müller
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2020-11-10 14:18 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
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 [this message]
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=4a3d24e0-399f-f509-9a5c-c66c57b2d28a@linux.ibm.com \
--to=mimu@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.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 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).