X-Git-Url: https://git.kernel.dk/?a=blobdiff_plain;ds=sidebyside;f=HOWTO;h=0b438714c56cba93b9f319178231b258bb2ee47e;hb=019b18e81e3b129bcf1a3e1bb10d172498f3cd2f;hp=08a2b68dac71cdbd2cd101d02fa2f2859b22cd8c;hpb=661598287ecc3b8987f312cf8403936552ce686a;p=fio.git

diff --git a/HOWTO b/HOWTO
index 08a2b68d..0b438714 100644
--- a/HOWTO
+++ b/HOWTO
@@ -285,6 +285,9 @@ bs_unaligned	If this option is given, any byte size value within bsrange
 		may be used as a block range. This typically wont work with
 		direct IO, as that normally requires sector alignment.
 
+zero_buffers	If this option is given, fio will init the IO buffers to
+		all zeroes. The default is to fill them with random data.
+
 nrfiles=int	Number of files to use for this job. Defaults to 1.
 
 openfiles=int	Number of files to keep open at the same time. Defaults to
@@ -474,6 +477,11 @@ runtime=int	Tell fio to terminate processing after the specified number
 		a specified job will run, so this parameter is handy to
 		cap the total runtime to a given time.
 
+time_based	If set, fio will run for the duration of the runtime
+		specified even if the file(s) are completey read or
+		written. It will simply loop over the same workload
+		as many times as the runtime allows.
+
 invalidate=bool	Invalidate the buffer/page cache parts for this file prior
 		to starting io. Defaults to true.
 
@@ -640,6 +648,9 @@ cpuload=int	If the job is a CPU cycle eater, attempt to use the specified
 cpuchunks=int	If the job is a CPU cycle eater, split the load into
 		cycles of the given time. In milliseconds.
 
+disk_util=bool	Generate disk utilization statistics, if the platform
+		supports it. Defaults to on.
+
 
 6.0 Interpreting the output
 ---------------------------
@@ -684,6 +695,7 @@ Client1 (g=0): err= 0:
     bw (KiB/s) : min=    0, max= 1196, per=51.00%, avg=664.02, stdev=681.68
   cpu        : usr=1.49%, sys=0.25%, ctx=7969
   IO depths    : 1=0.1%, 2=0.3%, 4=0.5%, 8=99.0%, 16=0.0%, 32=0.0%, >32=0.0%
+     issued r/w: total=0/32768, short=0/0
      lat (msec): 2=1.6%, 4=0.0%, 10=3.2%, 20=12.8%, 50=38.4%, 100=24.8%,
      lat (msec): 250=15.2%, 500=0.0%, 750=0.0%, 1000=0.0%, >=2048=0.0%
 
@@ -715,6 +727,8 @@ IO depths=	The distribution of io depths over the job life time. The
 		16= entries includes depths up to that value but higher
 		than the previous entry. In other words, it covers the
 		range from 16 to 31.
+IO issued=	The number of read/write requests issued, and how many
+		of them were short.
 IO latencies=	The distribution of IO completion latencies. This is the
 		time from when IO leaves fio and when it gets completed.
 		The numbers follow the same pattern as the IO depths,