From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 4260D1FF142 for ; Mon, 16 Feb 2026 10:39:24 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0E0D2A8D1; Mon, 16 Feb 2026 10:40:11 +0100 (CET) Message-ID: <35b2257e-c9a3-47a1-93b8-b6e720261947@proxmox.com> Date: Mon, 16 Feb 2026 10:39:34 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [pve-devel] [PATCH v3 qemu-server 10/10] RFC: add multiple iothreads support To: Proxmox VE development discussion References: <20250822141803.1658181-1-alexandre.derumier@groupe-cyllene.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1771234768592 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.016 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: 7EXYPNMN32J4UZ6YPTSNNEP7TMIEHXMH X-Message-ID-Hash: 7EXYPNMN32J4UZ6YPTSNNEP7TMIEHXMH X-MailFrom: f.ebner@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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/