X-Git-Url: https://git.kernel.dk/?p=fio.git;a=blobdiff_plain;f=HOWTO;h=3bda021d17c9090929d4276161b346242a0f27c4;hp=0c243076ef65be503d7fc17d63ba4f7737182ec9;hb=dc372f07b450e3b4c758d7a7fdaaca6c21843398;hpb=d2e268b09bc8ab95af81e5636608dcd93f40e4c1

diff --git a/HOWTO b/HOWTO
index 0c243076..3bda021d 100644
--- 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.
 
+			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
@@ -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
-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
@@ -723,7 +727,10 @@ runt=		The runtime of that thread
 	slat=	Submission latency (avg being the average, stdev being the
 		standard deviation). This is the time it took to submit
 		the io. For sync io, the slat is really the completion
-		latency, since queue/complete is one operation there.
+		latency, since queue/complete is one operation there. This
+		value can be in miliseconds or microseconds, fio will choose
+		the most appropriate base and print that. In the example
+		above, miliseconds is the best scale.
 	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,