From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C025A912C0 for ; Tue, 20 Dec 2022 12:24:57 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A2DB9323DD for ; Tue, 20 Dec 2022 12:24:27 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 20 Dec 2022 12:24:26 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 9939C45053 for ; Tue, 20 Dec 2022 12:24:26 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Tue, 20 Dec 2022 12:24:23 +0100 Message-Id: <20221220112423.99648-2-f.ebner@proxmox.com> X-Mailer: git-send-email 2.30.2 In-Reply-To: <20221220112423.99648-1-f.ebner@proxmox.com> References: <20221220112423.99648-1-f.ebner@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.026 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH v2 docs 2/2] qm: IO thread: mention that setting can also help with hangs X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Dec 2022 11:24:57 -0000 See https://bugzilla.kernel.org/show_bug.cgi?id=199727 Reported-by: Roland Kletzing Signed-off-by: Fiona Ebner --- New in v2. qm.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/qm.adoc b/qm.adoc index 900ecae..c3e876f 100644 --- a/qm.adoc +++ b/qm.adoc @@ -253,7 +253,9 @@ The option *IO Thread* can only be used when using a disk with the *VirtIO* controller, or with the *SCSI* controller, when the emulated controller type is *VirtIO SCSI single*. With *IO Thread* enabled, QEMU creates one I/O thread per storage controller, rather than handling all I/O in the main event loop or vCPU -threads. This can increase performance, because of improved work distribution. +threads. This can increase performance, because of improved work distribution +and also avoid hangs under very I/O-intensive host workloads, because other +threads won't be blocked waiting for I/O. [[qm_cpu]] -- 2.30.2