Lines Matching refs:the
4 Device Mapper supports the collection of I/O statistics on user-defined
11 the range specified.
14 in the same format as /sys/block/*/stat or /proc/diskstats (see:
16 provided: total time spent reading and writing. When the histogram
17 argument is used, the 14th parameter is reported that represents the
19 the @stats_print message to the appropriate DM device via dmsetup.
21 The reported times are in milliseconds and the granularity depends on
22 the kernel ticks. When the option precise_timestamps is used, the
26 region_id, that is assigned when the region is created. The region_id
27 must be supplied when querying statistics about the region, deleting the
29 request and process statistics for the same DM device without stepping
33 fallback to using vmalloc space. At most, 1/4 of the overall system
45 Create a new region and return the region_id.
53 "<area_size>" - the range is subdivided into areas each containing
55 "/<number_of_areas>" - the range is subdivided into the specified
64 instead of the "jiffies" variable. When this argument is
65 used, the resulting times are in nanoseconds instead of
69 numbers n1, n2, etc are times that represent the boundaries
70 of the histogram. If precise_timestamps is not used, the
72 nanoseconds. For each range, the kernel will report the
74 example, if we use "histogram:10,20,30", the kernel will
75 report four numbers a:b:c:d. a is the number of requests
76 that took 0-10 ms to complete, b is the number of requests
77 that took 10-20 ms to complete, c is the number of requests
78 that took 20-30 ms to complete and d is the number of
83 the userspace owner of the range. This groups ranges together
84 so that userspace programs can identify the ranges they
86 The kernel returns this string back in the output of
88 If we omit the number of optional arguments, program id must not
89 be a number, otherwise it would be interpreted as the number of
94 that is useful to the client program that created the range.
95 The kernel returns this string back in the output of
100 Delete the region with the specified id.
107 Clear all the counters except the in-flight i/o counters.
127 if they were specified when creating the region.
137 The index of the starting line in the output.
141 The number of lines to include in the output.
148 The first 11 counters have the same meaning as
153 1. the number of reads completed
154 2. the number of reads merged
155 3. the number of sectors read
156 4. the number of milliseconds spent reading
157 5. the number of writes completed
158 6. the number of writes merged
159 7. the number of sectors written
160 8. the number of milliseconds spent writing
161 9. the number of I/Os currently in progress
162 10. the number of milliseconds spent doing I/Os
163 11. the weighted number of milliseconds spent doing I/Os
166 12. the total time spent reading in milliseconds
167 13. the total time spent writing in milliseconds
171 Atomically print and then clear all the counters except the
172 in-flight i/o counters. Useful when the client consuming the
180 The index of the starting line in the output.
189 Store auxiliary data aux_data for the specified region.
195 The string that identifies data which is useful to the client
196 program that created the range. The kernel returns this
197 string back in the output of @stats_list message, but it
203 Subdivide the DM device 'vol' into 100 pieces and start collecting
208 Set the auxillary data string to "foo bar baz" (the escape for each
209 space must also be escaped, otherwise the shell will consume them):
213 List the statistics:
217 Print the statistics:
221 Delete the statistics: