Lines Matching refs:that

7 after the data was written.  At that point the original data that the
10 The solution is to ensure that the disk is actually storing what the
16 checksum for each sector as well as an incrementing counter that
18 for some protection schemes also that the I/O is written to the right
25 DIF and the other integrity extensions is that the protection format
53 read.  This means that Linux can DMA the data buffers to and from
57 is somewhat heavy to compute in software.  Benchmarks found that
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
88 disadvantage. It means that the protection information must be in a
89 format that can be understood by the disk.
105 that's attached to the I/O.
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
160 Layered block devices will need to pick a profile that's appropriate
161 for all subdevices.  blk_integrity_compare() can help with that.  DM
171     The normal filesystem is unaware that the underlying block device
190     A filesystem that is integrity-aware can prepare I/Os with IMD
202       added.  It is up to the caller to ensure that the bio does not
211     Filesystems that either generate their own integrity metadata or
231       understood by the target device with the notable exception that
233       I/O stack.  This implies that the pages added using this call
272       'verify_fn' verifies that the data buffer matches the integrity