The Compare command reads the logical blocks specified by the command from the medium and compares the data read to a comparison data buffer transferred as part of the command\&. If the data read from the controller and the comparison data buffer are equivalent with no miscompares, then the command completes successfully\&. If there is any miscompare, the command completes with an error of Compare Failure\&. If metadata is provided, then a comparison is also performed for the metadata\&.
.SH"OPTIONS"
.PP
\-s <slba>, \-\-start\-block=<slba>
.RS4
64\-bit address of the first block to access\&.
.RE
.PP
\-c <nlb>, \-\-block\-count=<nlb>
.RS4
Number of blocks to be accessed (zero\-based)\&.
.RE
.PP
\-z <size>, \-\-data\-size=<size>
.RS4
Size of data to be compared in bytes\&.
.RE
.PP
\-y <metasize>, \-\-metadata\-size=<metasize>
.RS4
Size of metadata to be trasnferred in bytes\&.
.RE
.PP
\-r <reftag>, \-\-ref\-tag=<regtag>
.RS4
Reference Tag for Protection Information
.RE
.PP
\-d <data\-file>, \-\-data=<data\-file>
.RS4
Data file\&.
.RE
.PP
\-M <meta>, \-\-metadata=<meta>
.RS4
Metadata file\&.
.RE
.PP
\-p <prinfo>, \-\-prinfo=<prinfo>
.RS4
Protection Information and check field\&.
.RE
.sp
+
.TS
allbox tab(:);
lt lt
lt lt
lt lt
lt lt
lt lt
lt lt.
T{
.sp
Bit
T}:T{
.sp
Description
T}
T{
.sp
3
T}:T{
.sp
PRACT: Protection Information Action\&. When set to 1, PI is stripped/inserted on read/write when the block format\(cqs metadata size is 8\&. When set to 0, metadata is passes\&.
T}
T{
.sp
2:0
T}:T{
.sp
PRCHK: Protection Information Check:
T}
T{
.sp
2
T}:T{
.sp
Set to 1 enables checking the guard tag
T}
T{
.sp
1
T}:T{
.sp
Set to 1 enables checking the application tag
T}
T{
.sp
0
T}:T{
.sp
Set to 1 enables checking the reference tag
T}
.TE
.sp1
.PP
\-m <appmask>, \-\-app\-tag\-mask=<appmask>
.RS4
App Tag Mask for Protection Information
.RE
.PP
\-a <apptag>, \-\-app\-tag=<apptag>
.RS4
App Tag for Protection Information
.RE
.PP
\-l, \-\-limited\-retry
.RS4
Number of limited attempts to media\&.
.RE
.PP
\-f, \-\-force\-unit\-access
.RS4
FUA option to guarantee that data is stored to media\&.
.RE
.PP
\-T <type>, \-\-dir\-type=<type>
.RS4
Optional directive type\&. The nvme\-cli only enforces the value be in the defined range for the directive type, though the NVMe specifcation (1\&.3a) defines only one directive, 01h, for write stream idenfiers\&.
.RE
.PP
\-S <spec>, \-\-dir\-spec=<spec>
.RS4
Optional field for directive specifics\&. When used with write streams, this value is defined to be the write stream identifier\&. The nvme\-cli will not validate the stream requested is within the controller\(cqs capabilities\&.
The optional data set management attributes for this command\&. The argument for this is the least significant 8 bits of the DSM field in a write command; the most significant 16 bits of the field come from the directive specific field, if used\&. This may be used to set attributes for the LBAs being written, like access frequency, type, latency, among other things, as well as yet to be defined types\&. Please consult the NVMe specification for detailed breakdown of how to use this field\&.