Lines Matching +full:in +full:- +full:application

12 application tried to write is most likely lost.
15 application meant it to. Recent additions to both the SCSI family
19 metadata (or protection information in SCSI terminology) includes a
21 ensures the individual sectors are written in the right order. And
27 technologies are working in their own isolated domains or at best
28 between adjacent nodes in the I/O path. The interesting thing about
30 is well defined and every node in the I/O path can verify the
47 in 520 byte sectors on disk. Data + IMD are interleaved when
54 scatter-gather lists.
60 Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
61 is somewhat heavy to compute in software. Benchmarks found that
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
68 generated by Linux or the application at very low cost (comparable to
71 The IP checksum is weaker than the CRC in terms of detecting bit
72 errors. However, the strength is really in the separation of the data
77 the choice in checksums is referred to as the Data Integrity
85 The data integrity framework in Linux enables protection information
89 The advantage to the integrity extensions in SCSI and SATA is that
90 they enable us to protect the entire path from application to storage
92 disadvantage. It means that the protection information must be in a
98 transport protocols completely transparent to the application.
102 concept of an end-to-end protection scheme is a layering violation.
103 It is completely unreasonable for an application to be aware whether
106 The data integrity support implemented in Linux attempts to hide this
107 from the application. As far as the application (and to some extent
118 16-bit value. The owner of this tag space is the owner of the block
119 device. I.e. the filesystem in most cases. The filesystem can use
134 -------
154 ----------------
156 Block devices can set up the integrity information in the integrity
157 sub-struture of the queue_limits structure.
162 will require extra work due to the application tag.
169 ---------------------
174 in case of a WRITE. A READ request will cause the I/O integrity
188 5.2 Integrity-Aware Filesystem
189 ------------------------------
191 A filesystem that is integrity-aware can prepare I/Os with IMD
192 attached. It can also use the application tag space if this is
204 change while I/O is in progress.
209 ---------------------------------------
220 stored in the integrity bio_vec list (similar to bio_alloc()).
230 the integrity metadata in the pages must be in a format
234 will be modified during I/O! The first reference tag in the
235 integrity metadata must have a value of bip->bip_sector.
238 there is room in the bip bio_vec array (nr_pages).
246 ----------------------------------------------------------------------
248 2007-12-24 Martin K. Petersen <martin.petersen@oracle.com>