docs: document no_completion_thread

Describe in the HOWTO and man page the windowsaio ioengine
no_completion_thread option.

Signed-off-by: Vincent Fu <vincent.fu@samsung.com>

diff --git a/HOWTO.rst b/HOWTO.rst
index 9b69eaee4ab923d593a02f2d04537d68a0d4371a..32fff5ecbde42cf894214f766f38130dba079760 100644 (file)
--- 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 <libblkio_wait_mode>`.
 
+.. 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 ba0272ce2f252815e8e12f56cc2eb0b49b370c9f..80bf3371a3556406cbcb29323bb21f55e769b9f9 100644 (file)
--- 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