X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=95d059e766e6399f29d8097331a076db4df29161;hp=4370c9f3607ff7fdc1b72f380dcc9eb3bf3662a3;hb=71619dc28506f7b7b40905b942e992b02f0d5b96;hpb=10cb47faf7283fe8c5b7da70078d96f447b5d62e;ds=sidebyside

diff --git a/HOWTO b/HOWTO
index 4370c9f3..95d059e7 100644
--- a/HOWTO
+++ b/HOWTO
@@ -503,7 +503,7 @@ cpuchunks=int	If the job is a CPU cycle eater, split the load into
 fio spits out a lot of output. While running, fio will display the
 status of the jobs created. An example of that would be:
 
-Threads running: 1: [_r] [24.79% done] [ 13509/  8334 kb/s] [eta 00h:01m:31s]
+Threads: 1: [_r] [24.8% done] [ 13509/  8334 kb/s] [eta 00h:01m:31s]
 
 The characters inside the square brackets denote the current status of
 each thread. The possible values (in typical life cycle order) are:
@@ -539,6 +539,7 @@ Client1 (g=0): err= 0:
     clat (msec): min=    0, max=  631, avg=48.50, stdev=86.82
     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%
 
 The client number is printed, along with the group id and error of that
 thread. Below is the io statistics, here for writes. In the order listed,
@@ -563,6 +564,11 @@ runt=		The runtime of that thread
 		same disk, since they are then competing for disk access.
 cpu=		CPU usage. User and system time, along with the number
 		of context switches this thread went through.
+IO depths=	The distribution of io depths over the job life time. The
+		numbers are divided into powers of 2, so for example 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.
 
 After each client has been listed, the group statistics are printed. They
 will look like this: