Home
last modified time | relevance | path

Searched refs:relative_throughput (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/drivers/md/
H A Ddm-ps-service-time.c35 unsigned int relative_throughput; member
97 pi->relative_throughput); in st_status()
101 pi->relative_throughput); in st_status()
118 unsigned int relative_throughput = 1; in st_add_path() local
164 pi->relative_throughput = relative_throughput; in st_add_path()
226 if (pi1->relative_throughput == pi2->relative_throughput) in st_compare_load()
234 !pi1->relative_throughput || !pi2->relative_throughput) in st_compare_load()
235 return pi2->relative_throughput - pi1->relative_throughput; in st_compare_load()
266 st1 = sz1 * pi2->relative_throughput; in st_compare_load()
267 st2 = sz2 * pi1->relative_throughput; in st_compare_load()
[all …]
/openbmc/linux/Documentation/admin-guide/device-mapper/
H A Ddm-service-time.rst18 [<repeat_count> [<relative_throughput>]]
24 <relative_throughput>:
34 <status> <fail-count> <in-flight-size> <relative_throughput>
41 <relative_throughput>:
59 1. If the paths have the same 'relative_throughput', skip
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'.
72 'relative_throughput' may be better. So compare 'relative_throughput'
[all …]