[PATCH] Remove the time init check

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index f36fc46e0b08d2aeed793519eae952b738b507f1..40f974cba7fdfce741c3ca641ef9975c8cd9b61c 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -179,7 +179,10 @@ siint      SI integer. A whole number value, which may contain a postfix
 bool   Boolean. Usually parsed as an integer, however only defined for
        true and false (1 and 0).
 irange Integer range with postfix. Allows value range to be given, such
 bool   Boolean. Usually parsed as an integer, however only defined for
        true and false (1 and 0).
 irange Integer range with postfix. Allows value range to be given, such

-       as 1024-4096. Also see siint.
+       as 1024-4096. A colon may also be used as the seperator, eg
+       1k:4k. If the option allows two sets of ranges, they can be
+       specified with a ',' or '/' delimiter: 1k-4k/8k-32k. Also see
+       siint.

 
 With the above in mind, here follows the complete list of fio job
 parameters.
 
 With the above in mind, here follows the complete list of fio job
 parameters.


@@ -500,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:
 
 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:
 
 The characters inside the square brackets denote the current status of
 each thread. The possible values (in typical life cycle order) are: