Fix headers for building with some older libs

[fio.git] / HOWTO

diff --git a/HOWTO b/HOWTO
index 4d103c846a4d7945f5cdb19d18a27c8b4139760c..3bda021d17c9090929d4276161b346242a0f27c4 100644 (file)
--- a/HOWTO
+++ b/HOWTO
@@ -343,6 +343,9 @@ ioengine=str        Defines how the job issues io to the file. The following
                                or receive, if the latter only the port
                                argument is used.
 
                                or receive, if the latter only the port
                                argument is used.
 

+                       netsplice Like net, but uses splice/vmsplice to
+                               map data and send/receive.
+

                        cpu     Doesn't transfer any data, but burns CPU
                                cycles according to the cpuload= and
                                cpucycle= options. Setting cpuload=85
                        cpu     Doesn't transfer any data, but burns CPU
                                cycles according to the cpuload= and
                                cpucycle= options. Setting cpuload=85


@@ -694,9 +697,10 @@ E          Thread exited, not reaped by main thread yet.
 _              Thread reaped.
 
 The other values are fairly self explanatory - number of threads
 _              Thread reaped.
 
 The other values are fairly self explanatory - number of threads

-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).
+currently running and doing io, rate of io since last check (read speed
+listed first, then write speed), 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
 
 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