From e63a0b2f293c6bcf3495c547eba414e1a6cf1840 Mon Sep 17 00:00:00 2001 From: Roman Pen Date: Sun, 27 Sep 2015 21:24:54 +0200 Subject: [PATCH] fio.1,HOWTO: keep 'iodepth_batch' option in sync Signed-off-by: Roman Pen Cc: fio@vger.kernel.org Signed-off-by: Jens Axboe --- HOWTO | 3 ++- fio.1 | 7 +++++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/HOWTO b/HOWTO index d3ead197..3049316a 100644 --- 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 c1cb2a5d..aea9f348 100644 --- 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 -- 2.25.1