Lines Matching refs:integrity
18 support for appending integrity metadata to an I/O. The integrity
29 DIF and the other integrity extensions is that the protection format
31 integrity of the I/O and reject it if corruption is detected. This
40 allow the operating system to interact with the integrity metadata
46 information to each sector. The data + integrity metadata is stored
53 encouraged them to allow separation of the data and integrity metadata
67 when writing and vice versa. This allows the integrity metadata to be
73 buffers and the integrity metadata. These two distinct buffers must
76 The separation of the data and integrity metadata buffers as well as
85 The data integrity framework in Linux enables protection information
89 The advantage to the integrity extensions in SCSI and SATA is that
106 The data integrity support implemented in Linux attempts to hide this
108 the kernel) is concerned, the integrity metadata is opaque information
113 intent is to move the integrity metadata calculation to userspace for
136 The data integrity patches add a new field to struct bio when
138 pointer to a struct bip which contains the bio integrity payload.
140 containing the integrity metadata and the required housekeeping
143 A kernel subsystem can enable data integrity protection on a bio by
147 Individual pages containing integrity metadata can subsequently be
157 disk, each block device has been extended with a block integrity
164 merging and splitting the integrity metadata.
179 is capable of sending/receiving integrity metadata. The IMD will
181 in case of a WRITE. A READ request will cause the I/O integrity
186 /sys/block/<bdev>/integrity/write_generate
190 /sys/block/<bdev>/integrity/read_verify
198 A filesystem that is integrity-aware can prepare I/Os with IMD
218 Filesystems that either generate their own integrity metadata or
225 Allocates the bio integrity payload and hangs it off of the bio.
227 stored in the integrity bio_vec list (similar to bio_alloc()).
229 The integrity payload will be freed at bio_free() time.
234 Attaches a page containing integrity metadata to an existing
237 the integrity metadata in the pages must be in a format
242 integrity metadata must have a value of bip->bip_sector.
248 contain the integrity metadata received from the storage device.
250 integrity upon completion.
256 To enable integrity exchange on a block device the gendisk must be
277 'generate_fn' generates appropriate integrity metadata (for WRITE).
279 'verify_fn' verifies that the data buffer matches the integrity
282 'tuple_size' must be set to match the size of the integrity