From: "Liu, Changcheng" <jerrliu@nvidia.com>
To: pbonzini@redhat.com, stefanha@redhat.com
Cc: virtualization@lists.linux.dev, changcheng.liu@aliyun.com
Subject: [PATCH] virtio_blk: add use_irq_affinity module parameter
Date: Sat, 1 Aug 2026 14:21:45 +0800 [thread overview]
Message-ID: <am2QeS/lS+Cova+I@yokbvdiprd370.nvidia.com> (raw)
When creating many virtio-blk devices, probe starts failing with
-ENOSPC (-28) because the system runs out of interrupt vectors:
virtio_blk virtioNNN: probe with driver virtio_blk failed with error -28
By default virtio-blk uses managed IRQ affinity, which reserves an
interrupt vector on every CPU for each device (about nr_cpus vectors per
device). On a host with many CPUs and many devices this exhausts the
vectors long before all devices are probed.
Add use_irq_affinity (default true, no behaviour change). Set it to 0 to
use unmanaged interrupts, so each device only uses a couple of vectors
instead of one per CPU, allowing far more devices to probe.
Signed-off-by: Liu, Changcheng <jerrliu@nvidia.com>
diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
index 32bf3ba07a9d..184f1c1f4485 100644
--- a/drivers/block/virtio_blk.c
+++ b/drivers/block/virtio_blk.c
@@ -41,6 +41,11 @@ static unsigned int poll_queues;
module_param(poll_queues, uint, 0644);
MODULE_PARM_DESC(poll_queues, "The number of dedicated virtqueues for polling I/O");
+static bool use_irq_affinity = true;
+module_param(use_irq_affinity, bool, 0644);
+MODULE_PARM_DESC(use_irq_affinity,
+ "Use managed IRQ affinity for virtqueues (default: true)");
+
static int major;
static DEFINE_IDA(vd_index_ida);
@@ -1016,7 +1021,8 @@ static int init_vq(struct virtio_blk *vblk)
}
/* Discover virtqueues and write information to configuration. */
- err = virtio_find_vqs(vdev, num_vqs, vqs, vqs_info, &desc);
+ err = virtio_find_vqs(vdev, num_vqs, vqs, vqs_info,
+ use_irq_affinity ? &desc : NULL);
if (err)
goto out;
--
2.43.7
next reply other threads:[~2026-08-01 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 6:21 Liu, Changcheng [this message]
2026-08-05 17:45 ` [PATCH] virtio_blk: add use_irq_affinity module parameter Stefan Hajnoczi
2026-08-06 2:40 ` Liu, Changcheng
2026-08-11 14:37 ` Stefan Hajnoczi
2026-08-12 2:25 ` Liu, Changcheng
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=am2QeS/lS+Cova+I@yokbvdiprd370.nvidia.com \
--to=jerrliu@nvidia.com \
--cc=changcheng.liu@aliyun.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@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