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
156 Block devices can set up the integrity information in the integrity
172 is capable of sending/receiving integrity metadata. The IMD will
174 in case of a WRITE. A READ request will cause the I/O integrity
179 /sys/block/<bdev>/integrity/write_generate
183 /sys/block/<bdev>/integrity/read_verify
191 A filesystem that is integrity-aware can prepare I/Os with IMD
211 Filesystems that either generate their own integrity metadata or
218 Allocates the bio integrity payload and hangs it off of the bio.
220 stored in the integrity bio_vec list (similar to bio_alloc()).
222 The integrity payload will be freed at bio_free() time.
227 Attaches a page containing integrity metadata to an existing
230 the integrity metadata in the pages must be in a format
235 integrity metadata must have a value of bip->bip_sector.
241 contain the integrity metadata received from the storage device.
243 integrity upon completion.