X-Git-Url: https://git.kernel.dk/?a=blobdiff_plain;f=fio.1;h=0e6095d6499b1f33e8cd1937a17ecbdd2fa548b5;hb=68b0316f581c3c881d7dbf7c9dafef4a10100a66;hp=5d0988b2cef496bfd8cd945aba0f332f04dee9ac;hpb=e76b1da43606f86fc23c8acb63114cba0d80a1c7;p=fio.git diff --git a/fio.1 b/fio.1 index 5d0988b2..0e6095d6 100644 --- a/fio.1 +++ b/fio.1 @@ -81,7 +81,11 @@ SI integer: a whole number, possibly containing a suffix denoting the base unit of the value. Accepted suffixes are `k', 'M', 'G', 'T', and 'P', denoting kilo (1024), mega (1024^2), giga (1024^3), tera (1024^4), and peta (1024^5) respectively. The suffix is not case sensitive. If prefixed with '0x', the -value is assumed to be base 16 (hexadecimal). +value is assumed to be base 16 (hexadecimal). A suffix may include a trailing +'b', for instance 'kb' is identical to 'k'. You can specify a base 10 value +by using 'KiB', 'MiB', 'GiB', etc. This is useful for disk drives where +values are often given in base 10 values. Specifying '30GiB' will get you +30*1000^3 bytes. .TP .I bool Boolean: a true or false value. `0' denotes false, `1' denotes true. @@ -211,14 +215,14 @@ same size. .TP .BI blocksize \fR=\fPint[,int] "\fR,\fB bs" \fR=\fPint[,int] Block size for I/O units. Default: 4k. Values for reads and writes can be -specified seperately in the format \fIread\fR,\fIwrite\fR, either of +specified separately in the format \fIread\fR,\fIwrite\fR, either of which may be empty to leave that value at its default. .TP .BI blocksize_range \fR=\fPirange[,irange] "\fR,\fB bsrange" \fR=\fPirange[,irange] Specify a range of I/O block sizes. The issued I/O unit will always be a multiple of the minimum size, unless \fBblocksize_unaligned\fR is set. Applies to both reads and writes if only one range is given, but can be specified -seperately with a comma seperating the values. Example: bsrange=1k-4k,2k-8k. +separately with a comma seperating the values. Example: bsrange=1k-4k,2k-8k. Also (see \fBblocksize\fR). .TP .BI bssplit \fR=\fPstr @@ -602,17 +606,13 @@ values are: .RS .TP .B md5 crc16 crc32 crc32c crc32c-intel crc64 crc7 sha256 sha512 sha1 -Store appropriate checksum in the header of each block. +Store appropriate checksum in the header of each block. crc32c-intel is +hardware accelerated SSE4.2 driven, falls back to regular crc32c if +not supported by the system. .TP .B meta Write extra information about each I/O (timestamp, block number, etc.). The -block number is verified. -.TP -.B pattern -Fill I/O buffers with a specific pattern that is used to verify. If the pattern -is < 4bytes, it can either be a decimal or a hexadecimal number. If the pattern -is > 4bytes, currently, it can only be a hexadecimal pattern starting with -either "0x" or "0X". +block number is verified. See \fBverify_pattern\fR as well. .TP .B null Pretend to verify. Used for testing internals. @@ -637,6 +637,15 @@ writing. It is swapped back before verifying. Write the verification header for this number of bytes, which should divide \fBblocksize\fR. Default: \fBblocksize\fR. .TP +.BI verify_pattern \fR=\fPstr +If set, fio will fill the io buffers with this pattern. Fio defaults to filling +with totally random bytes, but sometimes it's interesting to fill with a known +pattern for io verification purposes. Depending on the width of the pattern, +fio will fill 1/2/3/4 bytes of the buffer at the time(it can be either a +decimal or a hex number). The verify_pattern if larger than a 32-bit quantity +has to be a hex number that starts with either "0x" or "0X". Use with +\fBverify\fP=meta. +.TP .BI verify_fatal \fR=\fPbool If true, exit the job on the first observed verification failure. Default: false. @@ -653,6 +662,20 @@ allows them to have IO in flight while verifies are running. Tell fio to set the given CPU affinity on the async IO verification threads. See \fBcpus_allowed\fP for the format used. .TP +.BI verify_backlog \fR=\fPint +Fio will normally verify the written contents of a job that utilizes verify +once that job has completed. In other words, everything is written then +everything is read back and verified. You may want to verify continually +instead for a variety of reasons. Fio stores the meta data associated with an +IO block in memory, so for large verify workloads, quite a bit of memory would +be used up holding this meta data. If this option is enabled, fio will verify +the previously written blocks before continuing to write new ones. +.TP +.BI verify_backlog_batch \fR=\fPint +Control how many blocks fio will verify if verify_backlog is set. If not set, +will default to the value of \fBverify_backlog\fR (meaning the entire queue is +read back and verified). +.TP .B stonewall Wait for preceeding jobs in the job file to exit before starting this one. \fBstonewall\fR implies \fBnew_group\fR. @@ -762,6 +785,12 @@ your system doesn't have it mounted, you can do so with: Set the weight of the cgroup to this value. See the documentation that comes with the kernel, allowed values are in the range of 100..1000. .TP +.BI cgroup_nodelete \fR=\fPbool +Normally fio will delete the cgroups it has created after the job completion. +To override this behavior and to leave cgroups around after the job completion, +set cgroup_nodelete=1. This can be useful if one wants to inspect various +cgroup files after job completion. Default: false +.TP .BI uid \fR=\fPint Instead of running as the invoking user, set the user ID to this value before the thread/process does any work. @@ -977,7 +1006,8 @@ IO latency distribution (ms): .RE .SH AUTHORS .B fio -was written by Jens Axboe . +was written by Jens Axboe , +now Jens Axboe . .br This man page was written by Aaron Carroll based on documentation by Jens Axboe.