Home
last modified time | relevance | path

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

/linux-4.1.27/drivers/md/
Ddm-service-time.c33 unsigned relative_throughput; member
94 pi->relative_throughput); in st_status()
98 pi->relative_throughput); in st_status()
112 unsigned relative_throughput = 1; in st_add_path() local
138 (sscanf(argv[1], "%u%c", &relative_throughput, &dummy) != 1 || in st_add_path()
139 relative_throughput > ST_MAX_RELATIVE_THROUGHPUT)) { in st_add_path()
153 pi->relative_throughput = relative_throughput; in st_add_path()
207 if (pi1->relative_throughput == pi2->relative_throughput) in st_compare_load()
215 !pi1->relative_throughput || !pi2->relative_throughput) in st_compare_load()
216 return pi2->relative_throughput - pi1->relative_throughput; in st_compare_load()
[all …]
/linux-4.1.27/Documentation/device-mapper/
Ddm-service-time.txt15 Table parameters for each path: [<repeat_count> [<relative_throughput>]]
20 <relative_throughput>: The relative throughput value of the path
28 <relative_throughput>
32 <relative_throughput>: The relative throughput value of the path
44 ('in-flight-size' + 'size-of-incoming-io') / 'relative_throughput'
49 1. If the paths have the same 'relative_throughput', skip
53 and just compare the 'relative_throughput'.
55 3. If some paths have non-zero 'relative_throughput' and others
56 have zero 'relative_throughput', ignore those paths with zero
57 'relative_throughput'.
[all …]