Documentation/block/data-integrity.rst

10 corruption is done at read time which could potentially be months
40 allow the operating system to interact with the integrity metadata
53 encouraged them to allow separation of the data and integrity metadata
54 scatter-gather lists.
60 Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
63 performance for a number of workloads.  Some controllers allow a
64 lighter-weight checksum to be used when interfacing with the operating
66 The IP checksum received from the OS is converted to the 16-bit CRC
91 device.  However, at the same time this is also the biggest
102 concept of an end-to-end protection scheme is a layering violation.
117 Some storage devices allow each hardware sector to be tagged with a
118 16-bit value.  The owner of this tag space is the owner of the block
134 -------
154 ----------------
156 Block devices can set up the integrity information in the integrity
157 sub-struture of the queue_limits structure.
169 ---------------------
173     be automatically generated by the block layer at submit_bio() time
188 5.2 Integrity-Aware Filesystem
189 ------------------------------
191     A filesystem that is integrity-aware can prepare I/Os with IMD
198       To generate IMD for WRITE and to set up buffers for READ, the
202       sector must be set, and the bio should have all data pages
209 ---------------------------------------
222       The integrity payload will be freed at bio_free() time.
235       integrity metadata must have a value of bip->bip_sector.
246 ----------------------------------------------------------------------
248 2007-12-24 Martin K. Petersen <martin.petersen@oracle.com>