Lines Matching refs:in

17 				  * which to start mapping (in) */
19 				  * userspace cares about (in) */
20 	__u32	fm_flags;	 /* FIEMAP_FLAG_* flags for request (in/out) */
23 	__u32	fm_extent_count; /* size of fm_extents array (in) */
33 extent may end after fm_length. All offsets and lengths are in bytes.
35 Certain flags to modify the way in which mappings are looked up can be
36 set in fm_flags. If the kernel doesn't understand some particular
42 fiemap interface to grow in the future but without losing
45 fm_extent_count specifies the number of elements in the fm_extents[] array
48 fm_mapped_extents count will hold the number of extents needed in
52 The following flags can be set in fm_flags:
67 number of elements in the fiemap_extents[] array should be passed via
71 the maximum number of extents that can be mapped in the fm_extent[]
73 fm_extent_count. In that case, the last extent in the array will not
78 returned in fm_extents.
81 	__u64	fe_logical;  /* logical offset in bytes for the start of
83 	__u64	fe_physical; /* physical offset in bytes for the start
85 	__u64	fe_length;   /* length in bytes for the extent */
91 All offsets and lengths are in bytes and mirror those on disk.  It is valid
99 A special flag, FIEMAP_EXTENT_LAST is always set on the last extent in
103 Some flags are intentionally vague and will always be set in the
118 This is the last extent in the file. A mapping attempt past this
133 encoded (e.g. encrypted or compressed).  Reading the data in this
137 in-place by writing to the indicated location without the
148 The data in this extent has been encrypted by the file system.
208 The struct fieinfo should be passed in as received from ioctl_fiemap(). The
210 fiemap_check_flags finds invalid user flags, it will place the bad values in
216 For each extent in the request range, the file system should call
223 next free extent in the fm_extents array. 'General' extent flags will