From: Halil Pasic <pasic@linux.ibm.com>
To: Michael Mueller <mimu@linux.ibm.com>
Cc: Thomas Huth <thuth@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Cornelia Huck <cohuck@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: Thu, 12 Nov 2020 14:31:43 +0100 [thread overview]
Message-ID: <20201112143143.2e24b45c.pasic@linux.ibm.com> (raw)
In-Reply-To: <d13e61ad-8e98-4de8-141e-43eb7b513880@linux.ibm.com>
On Wed, 11 Nov 2020 13:49:08 +0100
Michael Mueller <mimu@linux.ibm.com> wrote:
> Halil,
>
> still I would like to know what the exact memory consumption per queue
> is that you are talking about. Have you made a calculation? Thanks.
Hi!
The default size for virtio-blk seems to be 256 ring entries, which
translates to 6668 bytes for the split ring(s). The queue size is user
configurable, and guest, in theory, can decide to have a smaller queue.
The indirect descriptors are allocated separately, and bounced via
swiotlb in case of secure guests.
Regards,
Halil
next prev parent reply other threads:[~2020-11-12 13:33 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
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 [this message]
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=20201112143143.2e24b45c.pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mimu@linux.ibm.com \
--cc=mst@redhat.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.