From 4c7a47cf0e27d43698555a0af135bfd657bddfda Mon Sep 17 00:00:00 2001 From: Fiona Ebner Date: Tue, 20 Dec 2022 12:24:22 +0100 Subject: [PATCH] qm: IO thread: be more precise about how QEMU handles IO Reported in the community forum[0]. The setting can already help with a single disk. Without the option, there is not one IO thread as the old wording suggested, but IO is handled in the main event loop or vCPU threads (see the kvm man page). [0]: https://forum.proxmox.com/threads/118390/post-518532 Signed-off-by: Fiona Ebner --- qm.adoc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/qm.adoc b/qm.adoc index 644ece5..900ecae 100644 --- a/qm.adoc +++ b/qm.adoc @@ -249,12 +249,11 @@ Note that *SSD emulation* is not supported on *VirtIO Block* drives. [[qm_hard_disk_iothread]] IO Thread ^^^^^^^^^ -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 this enabled, QEMU creates one I/O thread per storage controller, -rather than a single thread for all I/O. This can increase performance when -multiple disks are used and each disk has its own storage controller. +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. [[qm_cpu]] -- 2.39.2