Hello, Looks like I forgot to add this example how to reduce code under lock because add/del dest can run in parallel with scheduling, something that is a drawback in this solution: +static void ip_v
Hello, Me too, so I created a test for the eyes :) I hope it correctly implements the algorithm. include <stdio.h> include <stdlib.h> include <string.h> /* MAX_STEP: * 4: last has 3 times more chance
Sorry to have missed your message here. Yeah, this is what I mean. And in my case, the directors are local the to client, and each client only have 2 connections. If the 3th connection happens, it wi
Nice description :/ Yeah, prandom_u32_max is a good choice, I'll use it instead. I'm a little afraid that the 'steps' may make the starting dest not absolutely random, in terms of probability. For ex
Hello, ...order of added destinations,... ..."long connections are used". Is this a case where small number of connections are used? And the two connections relatively overload the real servers? You
For now, the start of the RR scheduler is in the order of dest service added, it will result in imbalance if the load balance is done in client side and long connect is used. For example, we have cli