From a64fd9c7994b51039b2fde851579c2453ddb35c0 Mon Sep 17 00:00:00 2001 From: Vincent Fu Date: Wed, 17 May 2023 14:44:49 +0000 Subject: [PATCH] docs: document no_completion_thread Describe in the HOWTO and man page the windowsaio ioengine no_completion_thread option. Signed-off-by: Vincent Fu --- HOWTO.rst | 4 ++++ fio.1 | 3 +++ 2 files changed, 7 insertions(+) diff --git a/HOWTO.rst b/HOWTO.rst index 9b69eaee..32fff5ec 100644 --- a/HOWTO.rst +++ b/HOWTO.rst @@ -3011,6 +3011,10 @@ with the caveat that when used on the command line, they must come after the performance. The default is to enable it only if :option:`libblkio_wait_mode=eventfd `. +.. option:: no_completion_thread : [windowsaio] + + Avoid using a separate thread for completion polling. + I/O depth ~~~~~~~~~ diff --git a/fio.1 b/fio.1 index ba0272ce..80bf3371 100644 --- a/fio.1 +++ b/fio.1 @@ -2765,6 +2765,9 @@ Use a busy loop with a non-blocking call to \fBblkioq_do_io()\fR. Enable the queue's completion eventfd even when unused. This may impact performance. The default is to enable it only if \fBlibblkio_wait_mode=eventfd\fR. +.TP +.BI (windowsaio)no_completion_thread +Avoid using a separate thread for completion polling. .SS "I/O depth" .TP .BI iodepth \fR=\fPint -- 2.25.1