Searched refs:weights (Results 1 – 4 of 4) sorted by relevance
128 connections to different real servers based on server weights129 in a round-robin manner. Servers with higher weights receive130 new connections first than those with less weights, and servers131 with higher weights get more connections than those with less132 weights and servers with equal weights get equal connections.295 until all slots in the table are filled. When using weights to297 tiled an amount proportional to the weights specified. The table299 multiplied by their respective weights.313 65521 or 131071. When using weights to allow destinations to315 proportional to the weights specified. The table needs to be large[all …]
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() local338 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()
237 kfree(arg->weight_set[j].weights); in free_choose_arg_map()312 w->weights = decode_array_32_alloc(p, end, &w->size); in decode_choose_arg()313 if (IS_ERR(w->weights)) { in decode_choose_arg()314 ret = PTR_ERR(w->weights); in decode_choose_arg()315 w->weights = NULL; in decode_choose_arg()
140 qopt.replace_params.weights[i] = weight; in ets_offload_change()