Lines Matching refs:I

14 support for appending integrity metadata to an I/O.  The integrity
18 for some protection schemes also that the I/O is written to the right
24 between adjacent nodes in the I/O path.  The interesting thing about
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
70 match up for an I/O to complete.
82 to be pinned to I/Os and sent to/received from controllers that
105 that's attached to the I/O.
108 generate the protection information for any I/O.  Eventually the
110 user data.  Metadata and other I/O that originates within the kernel
115 device.  I.e. the filesystem in most cases.  The filesystem can use
174     in case of a WRITE.  A READ request will cause the I/O integrity
190     A filesystem that is integrity-aware can prepare I/Os with IMD
203       change while I/O is in progress.
233       I/O stack.  This implies that the pages added using this call
234       will be modified during I/O!  The first reference tag in the
276       metadata per sector.  I.e. 8 for DIF and EPP.