projects
/
fio.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
malloc memory still needs to be aligned, if we are doing direct IO
[fio.git]
/
HOWTO
diff --git
a/HOWTO
b/HOWTO
index 0c243076ef65be503d7fc17d63ba4f7737182ec9..3af491325d3324b69117cc946728d7cd23ab8060 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
@@
-723,7
+726,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
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,
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,