Skip to content

Commit f0aec1d

Browse files
committed
docs: update docs for verify_mode=compare of io_uring_cmd
Add missing limitation of verify_mode=compare in io_uring_cmd ioengine. Data verification with NVMe COMPARE command has been introduced in Commit 6170d92 ("io_uring: Support Compare command for verification") and this should have documented COMPARE command only supports in case of data pattern verification. The two more options should be with --verify_mode=compare. verify_mode=compare verify=pattern verify_pattern=<pattern> Signed-off-by: Minwoo Im <[email protected]>
1 parent 43c67b9 commit f0aec1d

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

HOWTO.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2896,7 +2896,9 @@ with the caveat that when used on the command line, they must come after the
28962896
**read**
28972897
Use Read commands for data verification
28982898
**compare**
2899-
Use Compare commands for data verification
2899+
Use Compare commands for data verification. This option is only valid with
2900+
specific pattern(s), which means it *must* be given with `verify=pattern` and
2901+
`verify_pattern=<pattern>`.
29002902

29012903
.. option:: sg_write_mode=str : [sg]
29022904

fio.1

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2686,7 +2686,9 @@ Specifies the type of command to be used in the verification phase. Defaults to
26862686
Use Read commands for data verification
26872687
.TP
26882688
.B compare
2689-
Use Compare commands for data verification
2689+
Use Compare commands for data verification. This option is only valid with
2690+
specific pattern(s), which means it *must* be given with `verify=pattern` and
2691+
`verify_pattern=<pattern>`.
26902692
.TP
26912693
.RE
26922694
.RE

0 commit comments

Comments
 (0)