From: Halil Pasic <pasic@linux.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
Chandra Merla <cmerla@redhat.com>,
Stable@vger.kernel.org, Cornelia Huck <cohuck@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Eric Farman <farman@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Wei Wang <wei.w.wang@intel.com>,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [PATCH v1] s390/virtio_ccw: don't allocate/assign airqs for non-existing queues
Date: Fri, 4 Apr 2025 06:02:04 +0200 [thread overview]
Message-ID: <20250404060204.04db301d.pasic@linux.ibm.com> (raw)
In-Reply-To: <20250403103127-mutt-send-email-mst@kernel.org>
On Thu, 3 Apr 2025 10:35:33 -0400
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Thu, Apr 03, 2025 at 04:18:36PM +0200, Halil Pasic wrote:
> > On Wed, 2 Apr 2025 22:36:21 +0200
[..]
> >
> > 5.5.2 Virtqueues
> >
> > 0
> > inflateq
> > 1
> > deflateq
> > 2
> > statsq
> > 3
> > free_page_vq
> > 4
> > reporting_vq
>
> Indeed. Unfortunately, no one at all implemented this properly as
> per spec :(.
>
> Balloon is the worst offender here but other devices are broken
> too in some configurations.
>
>
> Given it has been like this for many years I'm inclined in this
> instance to fix the spec not the implementations.
>
I understand! For me at least knowing if we are going to change the
spec or the implementations is pretty important. It would probably
make sense to spin a patch for the spec, just for the unlikely case that
somebody did end up implementing this by the spec and wants to protest.
I think, a consequence of this design is that all queues need to be
created and allocated at initialization time.
I mean in the spec we have something like
"""
5.1.6.5.6.1 Driver Requirements: Automatic receive steering in multiqueue mode
The driver MUST configure the virtqueues before enabling them with the VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command.
"""
For example one could want to hotplug 2 more vCPUs and still have a
queue-pair per cpu (and a controlq). Those 2 extra queue-pairs could
in theory be allocated on-demand instead of having to allocate memory
for the rings for all the queues corresponding to the maxed out setup.
I've had a look at the Linux virtio-net and it does allocate all the
queues up front.
Also with this design, I believe we would effectively prohibit "holes".
Now if holes are prohibited, IMHO it does not make a whole lot of
sense for the virtio_find_vqs() to support holes. Because the holes
and a fair amount of complexity. Of course that would make sense as a
cleanup on top.
Regards,
Halil
next prev parent reply other threads:[~2025-04-04 4:02 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 20:36 [PATCH v1] s390/virtio_ccw: don't allocate/assign airqs for non-existing queues David Hildenbrand
2025-04-03 9:44 ` Thomas Huth
2025-04-03 12:45 ` Cornelia Huck
2025-04-03 12:57 ` Michael S. Tsirkin
2025-04-03 13:12 ` Christian Borntraeger
2025-04-03 14:18 ` Halil Pasic
2025-04-03 14:28 ` David Hildenbrand
2025-04-04 4:36 ` Halil Pasic
2025-04-04 10:00 ` David Hildenbrand
2025-04-04 10:55 ` David Hildenbrand
2025-04-04 13:36 ` Halil Pasic
2025-04-04 13:48 ` David Hildenbrand
2025-04-04 14:00 ` Halil Pasic
2025-04-04 14:17 ` David Hildenbrand
2025-04-04 15:39 ` Halil Pasic
2025-04-04 16:49 ` David Hildenbrand
2025-04-04 17:36 ` David Hildenbrand
2025-04-07 7:52 ` Michael S. Tsirkin
2025-04-07 8:17 ` David Hildenbrand
2025-04-07 8:34 ` Michael S. Tsirkin
2025-04-07 8:44 ` David Hildenbrand
2025-04-07 8:49 ` Michael S. Tsirkin
2025-04-07 8:54 ` David Hildenbrand
2025-04-07 8:58 ` Michael S. Tsirkin
2025-04-07 9:11 ` David Hildenbrand
2025-04-07 9:13 ` David Hildenbrand
2025-04-07 13:13 ` David Hildenbrand
2025-04-07 17:39 ` Daniel Verkamp
2025-04-07 18:47 ` David Hildenbrand
2025-04-07 21:09 ` Daniel Verkamp
2025-04-09 11:02 ` David Hildenbrand
2025-04-07 21:20 ` Michael S. Tsirkin
2025-04-09 10:46 ` David Hildenbrand
2025-04-09 10:56 ` Michael S. Tsirkin
2025-04-09 11:12 ` David Hildenbrand
2025-04-09 12:07 ` Michael S. Tsirkin
2025-04-09 12:24 ` David Hildenbrand
2025-04-09 16:08 ` Michael S. Tsirkin
2025-04-07 9:37 ` Michael S. Tsirkin
2025-04-07 13:12 ` Halil Pasic
2025-04-07 13:17 ` David Hildenbrand
2025-04-07 13:28 ` Cornelia Huck
2025-04-07 13:32 ` Michael S. Tsirkin
2025-04-07 17:26 ` Halil Pasic
2025-04-07 8:38 ` David Hildenbrand
2025-04-07 8:44 ` Michael S. Tsirkin
2025-04-07 8:50 ` David Hildenbrand
2025-04-07 9:22 ` David Hildenbrand
2025-04-07 8:41 ` Michael S. Tsirkin
2025-04-06 18:42 ` Michael S. Tsirkin
2025-04-07 7:18 ` David Hildenbrand
2025-04-07 8:54 ` Michael S. Tsirkin
2025-04-07 9:08 ` David Hildenbrand
2025-04-06 15:40 ` Michael S. Tsirkin
2025-04-03 14:35 ` Michael S. Tsirkin
2025-04-04 4:02 ` Halil Pasic [this message]
2025-04-04 5:33 ` Michael S. Tsirkin
2025-04-04 12:05 ` Halil Pasic
2025-04-10 18:44 ` David Hildenbrand
2025-04-11 11:11 ` Christian Borntraeger
2025-04-11 12:42 ` Heiko Carstens
2025-04-11 12:47 ` Christian Borntraeger
2025-04-11 13:34 ` David Hildenbrand
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=20250404060204.04db301d.pasic@linux.ibm.com \
--to=pasic@linux.ibm.com \
--cc=Stable@vger.kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cmerla@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.com \
--cc=svens@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=wei.w.wang@intel.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).