From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 docs 2/2] qm: IO thread: mention that setting can also help with hangs
Date: Tue, 20 Dec 2022 12:24:23 +0100 [thread overview]
Message-ID: <20221220112423.99648-2-f.ebner@proxmox.com> (raw)
In-Reply-To: <20221220112423.99648-1-f.ebner@proxmox.com>
See https://bugzilla.kernel.org/show_bug.cgi?id=199727
Reported-by: Roland Kletzing <devzero@web.de>
Signed-off-by: Fiona Ebner <f.ebner@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
next prev parent reply other threads:[~2022-12-20 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 11:24 [pve-devel] [PATCH v2 docs 1/2] qm: IO thread: be more precise about how QEMU handles IO Fiona Ebner
2022-12-20 11:24 ` Fiona Ebner [this message]
2022-12-21 13:48 ` [pve-devel] applied-series: " Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221220112423.99648-2-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox