Lines Matching +full:in +full:- +full:flight

5 Device Mapper supports the collection of I/O statistics on user-defined
7 collected so there isn't any performance impact.  Only bio-based DM
10 Each user-defined region specifies a starting sector, length and step.
11 Individual statistics will be collected for each step-sized area within
14 The I/O statistics counters for each step-sized area of a region are
15 in the same format as `/sys/block/*/stat` or `/proc/diskstats` (see:
16 Documentation/admin-guide/iostats.rst).  But two extra counters (12 and 13) are
22 The reported times are in milliseconds and the granularity depends on
24 reported times are in nanoseconds.
47 	  "-"
50 		a range of <length> 512-byte sectors
70 		used, the resulting times are in nanoseconds instead of
72 		to obtain than jiffies-based timestamps.
77 		times are in milliseconds, otherwise they are in
82 		that took 0-10 ms to complete, b is the number of requests
83 		that took 10-20 ms to complete, c is the number of requests
84 		that took 20-30 ms to complete and d is the number of
92 	  The kernel returns this string back in the output of
101 	  The kernel returns this string back in the output of
111 	Clear all the counters except the in-flight i/o counters.
133 	Print counters for each step-sized area of a region.
139 	  The index of the starting line in the output.
143 	  The number of lines to include in the output.
146 	Output format for each step-sized area of a region:
154 	  Please refer to Documentation/admin-guide/iostats.rst for details.
164 	  9. the number of I/Os currently in progress
170 	  12. the total time spent reading in milliseconds
171 	  13. the total time spent writing in milliseconds
175 	in-flight i/o counters.	 Useful when the client consuming the
183 	  The index of the starting line in the output.
199 	  string back in the output of @stats_list message, but it
208   dmsetup message vol 0 @stats_create - /100