X-Git-Url: https://git.kernel.dk/?a=blobdiff_plain;ds=sidebyside;f=HOWTO;h=c38266c2afe100fcf02106476c3ae52eb05e4ae1;hb=7437ee87e4f6457168e8440f9308b4296ddb9263;hp=4d103c846a4d7945f5cdb19d18a27c8b4139760c;hpb=8a35c71ea954894b26cb1af52f4089a228e1e68e;p=fio.git

diff --git a/HOWTO b/HOWTO
index 4d103c84..c38266c2 100644
--- a/HOWTO
+++ b/HOWTO
@@ -170,7 +170,8 @@ Some parameters take an option of a given type, such as an integer or
 a string. The following types are used:
 
 str	String. This is a sequence of alpha characters.
-int	Integer. A whole number value, can be negative.
+int	Integer. A whole number value, can be negative. If prefixed with
+	0x, the integer is assumed to be of base 16 (hexidecimal).
 siint	SI integer. A whole number value, which may contain a postfix
 	describing the base of the number. Accepted postfixes are k/m/g,
 	meaning kilo, mega, and giga. So if you want to specify 4096,
@@ -343,6 +344,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
@@ -571,9 +575,27 @@ verify=str	If writing to a file, fio can verify the file contents
 			md5	Use an md5 sum of the data area and store
 				it in the header of each block.
 
+			crc64	Use an experimental crc64 sum of the data
+				area and store it in the header of each
+				block.
+
 			crc32	Use a crc32 sum of the data area and store
 				it in the header of each block.
 
+			crc16	Use a crc16 sum of the data area and store
+				it in the header of each block.
+
+			crc7	Use a crc7 sum of the data area and store
+				it in the header of each block.
+
+			sha512	Use sha512 as the checksum function.
+
+			sha256	Use sha256 as the checksum function.
+
+			meta	Write extra information about each io
+				(timestamp, block number etc.). The block
+				number is verified.
+
 			null	Only pretend to verify. Useful for testing
 				internals with ioengine=null, not for much
 				else.
@@ -589,6 +611,23 @@ verifysort=bool	If set, fio will sort written verify blocks when it deems
 		can ignore this option unless doing huge amounts of really
 		fast IO where the red-black tree sorting CPU time becomes
 		significant.
+
+verify_offset=siint	Swap the verification header with data somewhere else
+			in the block before writing. Its swapped back before
+			verifying.
+
+verify_interval=siint	Write the verification header at a finer granularity
+			than the blocksize. It will be written for chunks the
+			size of header_interval. blocksize should divide this
+			evenly.
+
+verify_pattern=int	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. The verify_pattern cannot be larger than
+		a 32-bit quantity.
 		
 stonewall	Wait for preceeding jobs in the job file to exit, before
 		starting this one. Can be used to insert serialization
@@ -694,9 +733,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