- I guess 'write_log_log' was a copy-pasta typo.
- You used 'suffix' everywhere except for two places where you said
'postfix'.
Signed-off-by: Jens Axboe <axboe@kernel.dk>
one by appending a ':<nr>' to the end of the string given.
For a random read, it would look like 'rw=randread:8' for
passing in an offset modifier with a value of 8. If the
one by appending a ':<nr>' to the end of the string given.
For a random read, it would look like 'rw=randread:8' for
passing in an offset modifier with a value of 8. If the
- postfix is used with a sequential IO pattern, then the value
+ suffix is used with a sequential IO pattern, then the value
specified will be added to the generated offset for each IO.
For instance, using rw=write:4k will skip 4k for every
write. It turns sequential IO into sequential IO with holes.
specified will be added to the generated offset for each IO.
For instance, using rw=write:4k will skip 4k for every
write. It turns sequential IO into sequential IO with holes.
file. Can be used to store data of the bandwidth of the
jobs in their lifetime. The included fio_generate_plots
script uses gnuplot to turn these text files into nice
file. Can be used to store data of the bandwidth of the
jobs in their lifetime. The included fio_generate_plots
script uses gnuplot to turn these text files into nice
- graphs. See write_log_log for behaviour of given
- filename. For this option, the postfix is _bw.log.
+ graphs. See write_lat_log for behaviour of given
+ filename. For this option, the suffix is _bw.log.
write_lat_log=str Same as write_bw_log, except that this option stores io
submission, completion, and total latencies instead. If no
write_lat_log=str Same as write_bw_log, except that this option stores io
submission, completion, and total latencies instead. If no