[pve-devel] [PATCH v2 docs 2/2] qm: IO thread: mention that setting can also help with hangs

Fiona Ebner f.ebner at proxmox.com
Tue Dec 20 12:24:23 CET 2022


See https://bugzilla.kernel.org/show_bug.cgi?id=199727

Reported-by: Roland Kletzing <devzero at web.de>
Signed-off-by: Fiona Ebner <f.ebner at proxmox.com>
---

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






More information about the pve-devel mailing list