5 dm-service-time is a path selector module for device-mapper targets,
6 which selects a path with the shortest estimated service time for
9 The service time for each path is estimated by dividing the total size
10 of in-flight I/Os on a path with the performance value of the path.
11 The performance value is a relative throughput value among all paths
12 in a path-group, and it can be specified as a table argument.
14 The path selector name is 'service-time'.
16 Table parameters for each path:
18 [<repeat_count> [<relative_throughput>]]
20 The number of I/Os to dispatch using the selected
21 path before switching to the next path.
22 If not given, internal default is used. To check
23 the default value, see the activated table.
24 <relative_throughput>:
25 The relative throughput value of the path
26 among all paths in the path-group.
27 The valid range is 0-100.
28 If not given, minimum value '1' is used.
29 If '0' is given, the path isn't selected while
30 other paths having a positive value are available.
34 <status> <fail-count> <in-flight-size> <relative_throughput>
36 'A' if the path is active, 'F' if the path is failed.
38 The number of path failures.
40 The size of in-flight I/Os on the path.
41 <relative_throughput>:
42 The relative throughput value of the path
43 among all paths in the path-group.
49 dm-service-time adds the I/O size to 'in-flight-size' when the I/O is
50 dispatched and subtracts when completed.
51 Basically, dm-service-time selects a path having minimum service time
52 which is calculated by::
54 ('in-flight-size' + 'size-of-incoming-io') / 'relative_throughput'
56 However, some optimizations below are used to reduce the calculation
59 1. If the paths have the same 'relative_throughput', skip
60 the division and just compare the 'in-flight-size'.
62 2. If the paths have the same 'in-flight-size', skip the division
63 and just compare the 'relative_throughput'.
65 3. If some paths have non-zero 'relative_throughput' and others
66 have zero 'relative_throughput', ignore those paths with zero
67 'relative_throughput'.
69 If such optimizations can't be applied, calculate service time, and
71 If calculated service time is equal, the path having maximum
72 'relative_throughput' may be better. So compare 'relative_throughput'
78 In case that 2 paths (sda and sdb) are used with repeat_count == 128
79 and sda has an average throughput 1GB/s and sdb has 4GB/s,
80 'relative_throughput' value may be '1' for sda and '4' for sdb::
82 # echo "0 10 multipath 0 0 1 1 service-time 0 2 2 8:0 128 1 8:16 128 4" \
86 test: 0 10 multipath 0 0 1 1 service-time 0 2 2 8:0 128 1 8:16 128 4
89 test: 0 10 multipath 2 0 0 0 1 1 E 0 2 2 8:0 A 0 0 1 8:16 A 0 0 4
92 Or '2' for sda and '8' for sdb would be also true::
94 # echo "0 10 multipath 0 0 1 1 service-time 0 2 2 8:0 128 2 8:16 128 8" \
98 test: 0 10 multipath 0 0 1 1 service-time 0 2 2 8:0 128 2 8:16 128 8
101 test: 0 10 multipath 2 0 0 0 1 1 E 0 2 2 8:0 A 0 0 2 8:16 A 0 0 8