Merge branch 'master' into gfio

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index 662689ef304da064f677bdf5bf62b408e604abf3..eeaddbac69520f3997bebd5cc8c8f79149e23626 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -1150,12 +1150,6 @@ exec_postrun=str After the job completes, issue the command specified
 ioscheduler=str        Attempt to switch the device hosting the file to the specified
                io scheduler before running.
 
-cpuload=int    If the job is a CPU cycle eater, attempt to use the specified
-               percentage of CPU cycles.
-
-cpuchunks=int  If the job is a CPU cycle eater, split the load into
-               cycles of the given time. In microseconds.
-
 disk_util=bool Generate disk utilization statistics, if the platform
                supports it. Defaults to on.
 
@@ -1286,6 +1280,11 @@ that defines them is selected.
                enabled when polling for a minimum of 0 events (eg when
                iodepth_batch_complete=0).
 
+[cpu] cpuload=int Attempt to use the specified percentage of CPU cycles.
+
+[cpu] cpuchunks=int Split the load into cycles of the given time. In
+               microseconds.
+
 [netsplice] hostname=str
 [net] hostname=str The host name or IP address to use for TCP or UDP based IO.
                If the job is a TCP listener or UDP reader, the hostname is not
@@ -1382,7 +1381,8 @@ runt=             The runtime of that thread
                latency, since queue/complete is one operation there. This
                value can be in milliseconds or microseconds, fio will choose
                the most appropriate base and print that. In the example
-               above, milliseconds is the best scale.
+               above, milliseconds is the best scale. Note: in --minimal mode
+               latencies are always expressed in microseconds.
        clat=   Completion latency. Same names as slat, this denotes the
                time from submission to completion of the io pieces. For
                sync io, clat will usually be equal (or very close) to 0,
@@ -1474,14 +1474,14 @@ Split up, the format is as follows:
                Completion latency: min, max, mean, deviation (usec)
                Completion latency percentiles: 20 fields (see below)
                Total latency: min, max, mean, deviation (usec)
-               Bw: min, max, aggregate percentage of total, mean, deviation
+               Bw (KB/s): min, max, aggregate percentage of total, mean, deviation
        WRITE status:
                Total IO (KB), bandwidth (KB/sec), IOPS, runtime (msec)
                Submission latency: min, max, mean, deviation (usec)
                Completion latency: min, max, mean, deviation (usec)
                Completion latency percentiles: 20 fields (see below)
                Total latency: min, max, mean, deviation (usec)
-               Bw: min, max, aggregate percentage of total, mean, deviation
+               Bw (KB/s): min, max, aggregate percentage of total, mean, deviation
        CPU usage: user, system, context switches, major faults, minor faults
        IO depths: <=1, 2, 4, 8, 16, 32, >=64
        IO latencies microseconds: <=2, 4, 10, 20, 50, 100, 250, 500, 750, 1000