fio.1,HOWTO: keep 'iodepth_batch' option in sync

Signed-off-by: Roman Pen <r.peniaev@gmail.com>
Cc: fio@vger.kernel.org
Signed-off-by: Jens Axboe <axboe@fb.com>

diff --git a/HOWTO b/HOWTO
index d3ead19782796af8dc5b0b496a65318cc3bcf210..3049316a29aee80f28d0fd89ed686c943b704cb6 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -812,7 +812,8 @@ iodepth_batch_submit=int
 iodepth_batch=int This defines how many pieces of IO to submit at once.
                It defaults to 1 which means that we submit each IO
                as soon as it is available, but can be raised to submit
-               bigger batches of IO at the time.
+               bigger batches of IO at the time. If it is set to 0 the iodepth
+               value will be used.
 
 iodepth_batch_complete=int This defines how many pieces of IO to retrieve
                at once. It defaults to 1 which means that we'll ask

diff --git a/fio.1 b/fio.1
index c1cb2a5d71136dc7dfef0c55a3cd42b6a117389f..aea9f348512b2529fdd848459b76afd3e1908739 100644 (file)
--- a/fio.1
+++ b/fio.1
@@ -698,8 +698,11 @@ 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.
+.BI iodepth_batch \fR=\fPint "\fR,\fP iodepth_batch_submit" \fR=\fPint
+This defines how many pieces of IO to submit at once. It defaults to 1
+which means that we submit each IO as soon as it is available, but can
+be raised to submit bigger batches of IO at the time. If it is set to 0
+the \fBiodepth\fR value will be used.
 .TP
 .BI iodepth_batch_complete \fR=\fPint
 This defines how many pieces of IO to retrieve at once. It defaults to 1 which