`filename` semantic (which generates a file for each clone if not
specified, but lets all clones use the same file if set).
- See the :option:`filename` option for information on how to escape "``:``" and
- "``\``" characters within the directory path itself.
+ See the :option:`filename` option for information on how to escape "``:``"
+ characters within the directory path itself.
Note: To control the directory fio will use for internal state files
use :option:`--aux-path`.
by this option will be :option:`size` divided by number of files unless an
explicit size is specified by :option:`filesize`.
- Each colon and backslash in the wanted path must be escaped with a ``\``
+ Each colon in the wanted path must be escaped with a ``\``
character. For instance, if the path is :file:`/dev/dsk/foo@3,0:c` then you
would use ``filename=/dev/dsk/foo@3,0\:c`` and if the path is
- :file:`F:\\filename` then you would use ``filename=F\:\\filename``.
+ :file:`F:\\filename` then you would use ``filename=F\:\filename``.
On Windows, disk devices are accessed as :file:`\\\\.\\PhysicalDrive0` for
the first device, :file:`\\\\.\\PhysicalDrive1` for the second etc.
IO latency as well.
.. option:: registerfiles : [io_uring]
+
With this option, fio registers the set of files being used with the
kernel. This avoids the overhead of managing file counts in the kernel,
making the submission and completion part more lightweight. Required
(``blkparse <device> -o /dev/null -d file_for_fio.bin``).
You can specify a number of files by separating the names with a ':'
character. See the :option:`filename` option for information on how to
- escape ':' and '\' characters within the file names. These files will
+ escape ':' characters within the file names. These files will
be sequentially assigned to job clones created by :option:`numjobs`.
.. option:: read_iolog_chunked=bool
$ fio --read_iolog="<file1>:<file2>" --merge_blktrace_file="<output_file>"
Creating only the merged file can be done by passing the command line argument
-:option:`merge-blktrace-only`.
+:option:`--merge-blktrace-only`.
Scaling traces can be done to see the relative impact of any particular trace
being slowed down or sped up. :option:`merge_blktrace_scalars` takes in a colon