proxmox-mirrors/pve-docs
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-docs synced 2025-08-06 18:30:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

qm: IO-Thread: rework and add a bit more context

Browse Source 
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2022-12-21 14:48:10 +01:00
parent bcb4e590fb
commit afb9056593
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
qm.adoc
View File

@ -253,10 +253,10 @@ 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 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 *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 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. One benefit is better work distribution and utilization of the
and also avoid hangs under very I/O-intensive host workloads, because other underlying storage. Another benefit is reduced latency (hangs) in the guest for
threads won't be blocked waiting for I/O. very I/O-intensive host workloads, since neither the main thread nor a vCPU
thread can be blocked by disk I/O.
[[qm_cpu]] [[qm_cpu]]
CPU CPU