From: Randy Dunlap <rdunlap@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>, Alexander Graf <graf@amazon.com>
Cc: "Jason Wang" <jasowangio@gmail.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Shuah Khan" <skhan@linuxfoundation.org>,
virtualization@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, nh-open-source@amazon.com,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [RFC PATCH 12/12] virtio: guarantee a virtqueue can publish its first descriptor chain
Date: Sun, 9 Aug 2026 16:15:25 -0700 [thread overview]
Message-ID: <3f225be6-c87d-433d-9589-231d37ca6360@infradead.org> (raw)
In-Reply-To: <20260809184014-mutt-send-email-mst@kernel.org>
On 8/9/26 3:41 PM, Michael S. Tsirkin wrote:
> On Sun, Aug 09, 2026 at 06:20:10PM +0000, Alexander Graf wrote:
>> A device's pool is shared by every virtqueue it has and nothing
>> partitions it between them, so a virtqueue that asks late can get
>> nothing at all. virtnet_open() pre-fills the receive queues in index
>> order and discards the result, and a queue that came up with nothing is
>> one the device cannot signal a completion on.
>>
>> Withhold a range of the pool from ordinary claims and let a virtqueue
>> whose ring is empty draw on it for one descriptor chain.
> Why bother? one chain can just go inline in the ring.
https://people.kernel.org/tglx/notes-about-netiquette
or
https://subspace.kernel.org/etiquette.html
It would be good if 100s (or 1000s) or people didn't need to scan a 65 KB
email to see that most of it can be ignored.
--
~Randy
next prev parent reply other threads:[~2026-08-09 23:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 18:19 [RFC PATCH 00/12] virtio: support devices that own their virtqueue memory Alexander Graf
2026-08-09 18:20 ` [RFC PATCH 09/12] Documentation: virtio: describe the device memory buffer Alexander Graf
2026-08-09 22:09 ` Michael S. Tsirkin
2026-08-09 18:20 ` [RFC PATCH 10/12] virtio_ring: report a bounded pool's exhaustion as -ENOSPC Alexander Graf
2026-08-09 18:20 ` [RFC PATCH 11/12] virtio: expose device memory buffer occupancy over debugfs Alexander Graf
2026-08-09 18:20 ` [RFC PATCH 12/12] virtio: guarantee a virtqueue can publish its first descriptor chain Alexander Graf
2026-08-09 22:41 ` Michael S. Tsirkin
2026-08-09 23:15 ` Randy Dunlap [this message]
2026-08-10 6:23 ` [RFC PATCH 00/12] virtio: support devices that own their virtqueue memory Michael S. Tsirkin
2026-08-10 7:39 ` Graf (AWS), Alexander
2026-08-10 8:04 ` Michael S. Tsirkin
2026-08-10 8:25 ` Graf (AWS), Alexander
2026-08-10 19:14 ` Graf (AWS), Alexander
2026-08-10 21:42 ` Michael S. Tsirkin
2026-08-10 20:39 ` Stefan Hajnoczi
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=3f225be6-c87d-433d-9589-231d37ca6360@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=eperezma@redhat.com \
--cc=graf@amazon.com \
--cc=jasowangio@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nh-open-source@amazon.com \
--cc=pbonzini@redhat.com \
--cc=skhan@linuxfoundation.org \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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