Lines Matching refs:and

4 Modern filesystems feature checksumming of data and metadata to
21 Current storage controllers and devices implement various protective
22 measures, for instance checksumming and scrubbing.  But these
25 DIF and the other integrity extensions is that the protection format
26 is well defined and every node in the I/O path can verify the
27 integrity of the I/O and reject it if corruption is detected.  This
35 controller and storage device.  However, many controllers actually
38 the protection information to be transferred to and from their
44 transferred between the controller and target.  The T13 proposal is
48 520 (and 4104) byte sectors, we approached several HBA vendors and
49 encouraged them to allow separation of the data and integrity metadata
52 The controller will interleave the buffers on write and split them on
53 read.  This means that Linux can DMA the data buffers to and from
56 Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
63 when writing and vice versa.  This allows the integrity metadata to be
69 buffers and the integrity metadata.  These two distinct buffers must
72 The separation of the data and integrity metadata buffers as well as
75 bodies (T10, T13), Oracle and its partners are trying to standardize
82 to be pinned to I/Os and sent to/received from controllers that
85 The advantage to the integrity extensions in SCSI and SATA is that
93 and the block layer make things like hardware sector size and
103 from the application.  As far as the application (and to some extent
110 user data.  Metadata and other I/O that originates within the kernel
121 This also means that applications such as fsck and mkfs will need
135 containing the integrity metadata and the required housekeeping
139 calling bio_integrity_alloc(bio).  This will allocate and attach the
155 The profile contains callback functions for generating and verifying
156 the protection data, as well as getting and setting application tags.
158 merging and splitting the integrity metadata.
162 and MD linear, RAID0 and RAID1 are currently supported.  RAID4/5/6
177     IMD generation and verification can be toggled using the
181     and
197       To generate IMD for WRITE and to set up buffers for READ, the
200       Prior to calling this function, the bio data direction and start
201       sector must be set, and the bio should have all data pages
218       Allocates the bio integrity payload and hangs it off of the bio.
242       It is up to the receiver to process them and verify data
254       The blk_integrity struct is a template and should contain the
266       part of the userland API so chose it carefully and never change
276       metadata per sector.  I.e. 8 for DIF and EPP.