diff options
| author | Martin K. Petersen | 2014-09-26 19:20:03 -0400 |
|---|---|---|
| committer | Jens Axboe | 2014-09-27 09:14:51 -0600 |
| commit | 3aec2f41a8baeb70aa77556a4e4dcec7d9d70b4d (patch) | |
| tree | 2725a81cae556798bd3f363c4e8e5595c1ce1aaf /Documentation/ABI/testing/sysfs-block | |
| parent | 8288f496eb1b1905c425e92eaf1abbb29119217b (diff) | |
block: Add a disk flag to block integrity profile
So far we have relied on the app tag size to determine whether a disk
has been formatted with T10 protection information or not. However, not
all target devices provide application tag storage.
Add a flag to the block integrity profile that indicates whether the
disk has been formatted with protection information.
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-by: Sagi Grimberg <sagig@dev.mellanox.co.il>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'Documentation/ABI/testing/sysfs-block')
| -rw-r--r-- | Documentation/ABI/testing/sysfs-block | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/ABI/testing/sysfs-block b/Documentation/ABI/testing/sysfs-block index 279da08f7541..8df003963d99 100644 --- a/Documentation/ABI/testing/sysfs-block +++ b/Documentation/ABI/testing/sysfs-block @@ -53,6 +53,14 @@ Description: 512 bytes of data. +What: /sys/block/<disk>/integrity/device_is_integrity_capable +Date: July 2014 +Contact: Martin K. Petersen <martin.petersen@oracle.com> +Description: + Indicates whether a storage device is capable of storing + integrity metadata. Set if the device is T10 PI-capable. + + What: /sys/block/<disk>/integrity/write_generate Date: June 2008 Contact: Martin K. Petersen <martin.petersen@oracle.com> |