Long line style fix + comment

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index 5a55c1a21b574a3adba1aa52f4f0fee6f42458c7..731684cb9d62c7766155ba050ee66178ea19c428 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -590,7 +590,9 @@ cpumask=int Set the CPU affinity of this job. The parameter given is a
 
 cpus_allowed=str Controls the same options as cpumask, but it allows a text
                setting of the permitted CPUs instead. So to use CPUs 1 and
-               5, you would specify cpus_allowed=1,5.
+               5, you would specify cpus_allowed=1,5. This options also
+               allows a range of CPUs. Say you wanted a binding to CPUs
+               1, 5, and 8-15, you would set cpus_allowed=1,5,8-15.
 
 startdelay=time        Start this job the specified number of seconds after fio
                has started. Only useful if the job file contains several
@@ -867,6 +869,18 @@ gtod_reduce=bool Enable all of the gettimeofday() reducing options
                we only do about 0.4% of the gtod() calls we would have
                done if all time keeping was enabled.
 
+gtod_cpu=int   Sometimes it's cheaper to dedicate a single thread of
+               execution to just getting the current time. Fio (and
+               databases, for instance) are very intensive on gettimeofday()
+               calls. With this option, you can set one CPU aside for
+               doing nothing but logging current time to a shared memory
+               location. Then the other threads/processes that run IO
+               workloads need only copy that segment, instead of entering
+               the kernel with a gettimeofday() call. The CPU set aside
+               for doing these time calls will be excluded from other
+               uses. Fio will manually clear it from the CPU mask of other
+               jobs.
+
 
 6.0 Interpreting the output
 ---------------------------