| /Linux-v5.4/net/netfilter/ipvs/ |
| D | Kconfig | 128 connections to different real servers based on server weights
129 in a round-robin manner. Servers with higher weights receive
130 new connections first than those with less weights, and servers
131 with higher weights get more connections than those with less
132 weights and servers with equal weights get equal connections.
284 until all slots in the table are filled. When using weights to
286 tiled an amount proportional to the weights specified. The table
288 multiplied by their respective weights.
302 65521 or 131071. When using weights to allow destinations to
304 proportional to the weights specified. The table needs to be large
[all …]
|
| /Linux-v5.4/net/ceph/crush/ |
| D | mapper.c | 314 return arg->weight_set[position].weights; in get_choose_arg_weights()
334 __u32 *weights = get_choose_arg_weights(bucket, arg, position); in bucket_straw2_choose() local
338 dprintk("weight 0x%x item %d\n", weights[i], ids[i]); in bucket_straw2_choose()
339 if (weights[i]) { in bucket_straw2_choose()
361 draw = div64_s64(ln, weights[i]); in bucket_straw2_choose()
|
| /Linux-v5.4/Documentation/block/ |
| D | bfq-iosched.rst | 130 among I/O-bound applications in proportion their weights, with any
319 weights can be assigned to processes only indirectly, through I/O
325 applications. Unset this tunable if you need/want to control weights.
356 case of differentiated weights or differentiated I/O-request lengths.
398 In the presence of differentiated weights or I/O-request sizes, both
495 weights section in 3. What are BFQ's tunables and how to properly configure BFQ?
498 Read-only parameter, used to show the weights of the currently active
513 device bandwidth, according to group weights. For example, a group
520 group in proportion to their weights. In particular, this implies
570 linear mapping between ioprio and weights, described at the beginning
[all …]
|
| /Linux-v5.4/block/ |
| D | Kconfig.iosched | 25 of the device among all processes according to their weights,
|
| /Linux-v5.4/include/linux/crush/ |
| D | crush.h | 150 __u32 *weights; /*!< 16.16 fixed point weights member
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-driver-hid-roccat-kone | 91 Description: The mouse can be equipped with one of four supplied weights
96 The values map to the weights as follows:
|
| /Linux-v5.4/Documentation/driver-api/thermal/ |
| D | power_allocator.rst | 243 Cooling device weights
256 `thermal_zone_device_register()` (i.e., platform code), then weights
|
| D | sysfs-api.rst | 324 devices have a weight of 0. If all weights are 0, then
|
| /Linux-v5.4/net/ceph/ |
| D | osdmap.c | 164 kfree(arg->weight_set[j].weights); in free_choose_arg_map()
239 w->weights = decode_array_32_alloc(p, end, &w->size); in decode_choose_arg()
240 if (IS_ERR(w->weights)) { in decode_choose_arg()
241 ret = PTR_ERR(w->weights); in decode_choose_arg()
242 w->weights = NULL; in decode_choose_arg()
|
| /Linux-v5.4/Documentation/vm/ |
| D | balance.rst | 57 fancy, we could assign different weights to free pages in different
|
| /Linux-v5.4/drivers/staging/media/ipu3/ |
| D | ipu3-css-params.c | 2453 acc->ae.weights[i] = acc_user->ae.weights[i]; in imgu_css_cfg_acc()
2459 acc->ae.weights[i] = acc_old->ae.weights[i]; in imgu_css_cfg_acc()
2468 acc->ae.weights[i] = weight_def; in imgu_css_cfg_acc()
|
| D | ipu3-abi.h | 1229 struct ipu3_uapi_ae_weight_elem weights[IPU3_UAPI_AE_WEIGHTS] member
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-diff.txt | 279 - WEIGHT-A/WEIGHT-B being user supplied weights in the the '-c' option
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-design-CFS.rst | 68 rq->cfs.load value, which is the sum of the weights of the tasks queued on the
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 100 Currently allowed range of weights is from 10 to 1000.
|
| /Linux-v5.4/drivers/staging/media/ipu3/include/ |
| D | intel-ipu3.h | 247 struct ipu3_uapi_ae_weight_elem weights[ member
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 579 A parent's resource is distributed by adding up the weights of all
586 All weights are in the range [1, 10000] with the default at 100. This
1581 $MAJ:$MIN device numbers and not ordered. The weights are in
2410 mapped nice levels to cgroup weights. This worked for some cases but
|
| /Linux-v5.4/Documentation/networking/ |
| D | scaling.rst | 70 relative weights.
|
| /Linux-v5.4/Documentation/trace/ |
| D | histogram.rst | 1012 weights in terms of skb length for each callpath that leads to a
|
