Support > 4 byte verify write patterns
This is the patch I have to write/read/verify hex patterns of size > 4
bytes. I have tested these on hard drives and did not see any
performance change. I am assuming the performance drop if any might show
up in the read phase for probably solid state drives and maybe it can be
worked around using the asynchronous verify flag.
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
diff --git a/fio.1 b/fio.1
index f216b4c..4445d0a 100644
--- a/fio.1
+++ b/fio.1
@@ -583,9 +583,10 @@
block number is verified.
.TP
.B pattern
-Fill I/O buffers with a specific pattern that is used to verify. The pattern is
-specified by appending `:\fIint\fR' to the parameter. \fIint\fR cannot be larger
-than 32-bits.
+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".
.TP
.B null
Pretend to verify. Used for testing internals.