X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=c17d29e5652a864de9d3ffbf0763f68be6e4a4c1;hp=78a9be037839b1692bdca1e64f6283daaa3aad4c;hb=6043c5790f9978814ec25e3ea8f4d574daf6266e;hpb=fb19ce5a38404dcb14334a2c2300fd065958a28e

diff --git a/HOWTO b/HOWTO
index 78a9be03..c17d29e5 100644
--- a/HOWTO
+++ b/HOWTO
@@ -454,7 +454,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] [eta 00h:01m:31s]
+Threads running: 1: [_r] [24.79% 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:
@@ -476,9 +476,9 @@ E		Thread exited, not reaped by main thread yet.
 _		Thread reaped.
 
 The other values are fairly self explanatory - number of threads
-currently running and doing io, and the estimated completion percentage
-and time for the running group. It's impossible to estimate runtime
-of the following groups (if any).
+currently running and doing io, rate of io since last check, and the estimated
+completion percentage and time for the running group. It's impossible to
+estimate runtime of the following groups (if any).
 
 When fio is done (or interrupted by ctrl-c), it will show the data for
 each thread, group of threads, and disks in that order. For each data