From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 qemu-server 10/10] RFC: add multiple iothreads support
Date: Mon, 16 Feb 2026 10:39:34 +0100 [thread overview]
Message-ID: <35b2257e-c9a3-47a1-93b8-b6e720261947@proxmox.com> (raw)
In-Reply-To: <mailman.302.1755872323.385.pve-devel@lists.proxmox.com>
Am 22.08.25 um 4:18 PM schrieb Alexandre Derumier:
> + iothreads => {
> + optional => 1,
> + type => 'string',
> + verbose_description =>
> + "Create multiple iothreads and share them between disks where iothread is enabled."
> + . "Iothreads can be optionally pinned to specific host cpu. (Ideally on different"
> + . "host cores than the vm vcpus)",
> + description => "Multiple iothreads configuration.",
> + format => $PVE::QemuServer::DriveDevice::iothreads_fmt,
> + },
Multiple iothreads in particular means that block jobs might be
executing in more different threads than before. There might be buggy
edge cases/races lurking. This came up recently (see the lower half of
[0]), so I'd like to start out with stating that this feature is a tech
preview in the schema description. We can drop this label later if
nothing actually comes up.
[0]: https://lore.kernel.org/qemu-devel/aYTE9hf0mMTOUUTJ@redhat.com/
prev parent reply other threads:[~2026-02-16 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250822141803.1658181-1-alexandre.derumier@groupe-cyllene.com>
2025-08-22 14:17 ` [pve-devel] [PATCH v3 qemu-server 01/10] introduce DriveDevice module Alexandre Derumier via pve-devel
2025-10-02 12:19 ` [pve-devel] applied: " Fiona Ebner
2025-08-22 14:17 ` [pve-devel] [PATCH v3 qemu-server 02/10] add print_drivedevice_controller && print_drivedevice_iothread Alexandre Derumier via pve-devel
2025-10-02 12:30 ` Fiona Ebner
2025-08-22 14:17 ` [pve-devel] [PATCH v3 qemu-server 03/10] hotplug: drive controller : use print_drivedevice_iothread && print_drivedevice_controller Alexandre Derumier via pve-devel
2025-08-22 14:17 ` [pve-devel] [PATCH v3 qemu-server 04/10] pci: add get_pci_addr Alexandre Derumier via pve-devel
2025-08-22 14:17 ` [pve-devel] [PATCH v3 qemu-server 05/10] qmphelpers: add qmp_deviceadd && qmp_devicedel Alexandre Derumier via pve-devel
2025-08-22 14:17 ` [pve-devel] [PATCH v3 qemu-server 06/10] convert drive device to json format Alexandre Derumier via pve-devel
2025-10-02 13:20 ` Fiona Ebner
2025-08-22 14:17 ` [pve-devel] [PATCH v3 qemu-server 07/10] convert iothread to json Alexandre Derumier via pve-devel
2025-08-22 14:18 ` [pve-devel] [PATCH v3 qemu-server 08/10] convert disk controller device to json format Alexandre Derumier via pve-devel
2025-08-22 14:18 ` [pve-devel] [PATCH v3 qemu-server 09/10] tests: cfg2cmd: convert drive devices " Alexandre Derumier via pve-devel
2025-08-22 14:18 ` [pve-devel] [PATCH v3 qemu-server 10/10] RFC: add multiple iothreads support Alexandre Derumier via pve-devel
2026-02-16 9:39 ` Fiona Ebner [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=35b2257e-c9a3-47a1-93b8-b6e720261947@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.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.