Lines Matching full:protection

16 protocols (SBC Data Integrity Field, SCC protection proposal) as well
17 as SATA/T13 (External Path Protection) try to remedy this by adding
19 metadata (or protection information in SCSI terminology) includes a
22 for some protection schemes also that the I/O is written to the right
29 DIF and the other integrity extensions is that the protection format
42 the protection information to be transferred to and from their
45 The SCSI Data Integrity Field works by appending 8 bytes of protection
85 The data integrity framework in Linux enables protection information
92 disadvantage. It means that the protection information must be in a
101 protection information to send to a disk.  Consequently, the very
102 concept of an end-to-end protection scheme is a layering violation.
112 generate the protection information for any I/O.  Eventually the
143 A kernel subsystem can enable data integrity protection on a bio by
156 Because the format of the protection data is tied to the physical
162 the protection data, as well as getting and setting application tags.
226       nr_pages indicate how many pages of protection data need to be