Lines Matching +full:message +full:- +full:based
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
16 Documentation/admin-guide/iostats.rst). But two extra counters (12 and 13) are
20 the @stats_print message to the appropriate DM device via dmsetup.
47 "-"
50 a range of <length> 512-byte sectors
72 to obtain than jiffies-based timestamps.
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
93 @stats_list message, but it doesn't use it for anything else.
102 @stats_list message, but it doesn't use this value for anything.
111 Clear all the counters except the in-flight i/o counters.
133 Print counters for each step-sized area of a region.
146 Output format for each step-sized area of a region:
154 Please refer to Documentation/admin-guide/iostats.rst for details.
175 in-flight i/o counters. Useful when the client consuming the
199 string back in the output of @stats_list message, but it
208 dmsetup message vol 0 @stats_create - /100
213 dmsetup message vol 0 @stats_set_aux 0 foo\\ bar\\ baz
217 dmsetup message vol 0 @stats_list
221 dmsetup message vol 0 @stats_print 0
225 dmsetup message vol 0 @stats_delete 0