Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
Cc: Demi Marie Obenour <demiobenour@gmail.com>,
	virtio-comment <virtio-comment@lists.linux.dev>
Subject: Re: Max number of descriptors in a virtio-blk chain
Date: Wed, 22 Apr 2026 14:11:04 -0400	[thread overview]
Message-ID: <20260422181104.GC498202@fedora> (raw)
In-Reply-To: <aejrkBlN3VtoNFwx@fedora>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

On Wed, Apr 22, 2026 at 05:38:56PM +0200, Matias Ezequiel Vara Larsen wrote:
> Hello,
> 
> On Wed, Apr 22, 2026 at 04:02:06AM -0400, Demi Marie Obenour wrote:
> > Is there a limit to the number of descriptors that a virtio-blk driver
> > can use in a request?  In at least Cloud Hypervisor's implementation,
> 
> I think this is limited to the number of descriptors that you expose to
> the device in the descriptor ring. In addition, I think the index is 16
> bits long.

Virtqueue size is the upper limit. There are also additional
Configuration Space fields that limit virtio-blk requests:

- seg_max: max number of descriptors in a request
- max_discard_seg: max number of descriptors for discard requests
- max_write_zeroes_seg: max number of descriptors for write zeroes
  requests
- max_secure_erase_seg: max number of descriptors for secure erase
  requests

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

      reply	other threads:[~2026-04-22 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22  8:02 Max number of descriptors in a virtio-blk chain Demi Marie Obenour
2026-04-22 15:38 ` Matias Ezequiel Vara Larsen
2026-04-22 18:11   ` Stefan Hajnoczi [this message]

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=20260422181104.GC498202@fedora \
    --to=stefanha@redhat.com \
    --cc=demiobenour@gmail.com \
    --cc=mvaralar@redhat.com \
    --cc=virtio-comment@lists.linux.dev \
    /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