blob: 9375d23a24e7aba97504d743e77d3b78f4d72493 [file] [log] [blame]
Martin K. Petersen2341c2f2014-09-26 19:20:07 -04001#ifndef _LINUX_T10_PI_H
2#define _LINUX_T10_PI_H
3
4#include <linux/types.h>
5#include <linux/blkdev.h>
6
7/*
Christoph Hellwig8475c812016-09-11 19:35:41 +02008 * A T10 PI-capable target device can be formatted with different
9 * protection schemes. Currently 0 through 3 are defined:
10 *
11 * Type 0 is regular (unprotected) I/O
12 *
13 * Type 1 defines the contents of the guard and reference tags
14 *
15 * Type 2 defines the contents of the guard and reference tags and
16 * uses 32-byte commands to seed the latter
17 *
18 * Type 3 defines the contents of the guard tag only
19 */
20enum t10_dif_type {
21 T10_PI_TYPE0_PROTECTION = 0x0,
22 T10_PI_TYPE1_PROTECTION = 0x1,
23 T10_PI_TYPE2_PROTECTION = 0x2,
24 T10_PI_TYPE3_PROTECTION = 0x3,
25};
26
27/*
Martin K. Petersen2341c2f2014-09-26 19:20:07 -040028 * T10 Protection Information tuple.
29 */
30struct t10_pi_tuple {
31 __be16 guard_tag; /* Checksum */
32 __be16 app_tag; /* Opaque storage */
33 __be32 ref_tag; /* Target LBA or indirect LBA */
34};
35
36
Eric Biggers869ab902017-03-24 18:03:48 -070037extern const struct blk_integrity_profile t10_pi_type1_crc;
38extern const struct blk_integrity_profile t10_pi_type1_ip;
39extern const struct blk_integrity_profile t10_pi_type3_crc;
40extern const struct blk_integrity_profile t10_pi_type3_ip;
Martin K. Petersen2341c2f2014-09-26 19:20:07 -040041
42#endif