First snapshot of FIO for Windows

[fio.git] / fio.1

diff --git a/fio.1 b/fio.1
index ab147f28ce8a1bdc227c5ff23eb6fc77e14bab0c..8d5baa831d1c90f63ef60810a560b4238810cae4 100644 (file)
--- a/fio.1
+++ b/fio.1
@@ -331,7 +331,13 @@ coalescing adjacents IOs into a single submission.
 Linux native asynchronous I/O.
 .TP
 .B posixaio
-glibc POSIX asynchronous I/O using \fIaio_read\fR\|(3) and \fIaio_write\fR\|(3).
+POSIX asynchronous I/O using \fIaio_read\fR\|(3) and \fIaio_write\fR\|(3).
+.TP
+.B solarisaio
+Solaris native asynchronous I/O.
+.TP
+.B windowsaio
+Windows native asynchronous I/O.
 .TP
 .B mmap
 File is memory mapped with \fImmap\fR\|(2) and data copied using
@@ -381,7 +387,11 @@ Loads an external I/O engine object file.  Append the engine filename as
 .BI iodepth \fR=\fPint
 Number of I/O units to keep in flight against the file. Note that increasing
 iodepth beyond 1 will not affect synchronous ioengines (except for small
-degress when verify_async is in use).  Default: 1.
+degress when verify_async is in use). Even async engines my impose OS
+restrictions causing the desired depth not to be achieved.  This may happen on
+Linux when using libaio and not setting \fBdirect\fR=1, since buffered IO is
+not async on that OS. Keep an eye on the IO depth distribution in the
+fio output to verify that the achieved depth is as expected. Default: 1.
 .TP
 .BI iodepth_batch \fR=\fPint
 Number of I/Os to submit at once.  Default: \fBiodepth\fR.