Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+net\-next\s+v2\]\s+net\:\s+ipvs\:\s+randomize\s+starting\s+destination\s+of\s+RR\/WRR\s+scheduler\s*$/: 5 ]

Total 5 documents matching your query.

1. Re: [PATCH net-next v2] net: ipvs: randomize starting destination of RR/WRR scheduler (score: 1)
Author: Menglong Dong <menglong8.dong@xxxxxxxxx>
Date: Sun, 15 May 2022 21:47:19 +0800
Yes, we need a more nice way to do this work. It's easy for RR, but a little complex for WRR, after I figure out how WRR works. Using a user tool to add dests in random order is an option, which I th
/html/lvs-devel/2022-05/msg00011.html (13,483 bytes)

2. Re: [PATCH net-next v2] net: ipvs: randomize starting destination of RR/WRR scheduler (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Thu, 12 May 2022 13:33:39 +0300 (EEST)
Hello, If there is some more clever way to add randomness. The problem is that random start should be applied after initial configuration only. But there is no clear point between where configuration
/html/lvs-devel/2022-05/msg00009.html (12,066 bytes)

3. Re: [PATCH net-next v2] net: ipvs: randomize starting destination of RR/WRR scheduler (score: 1)
Author: Menglong Dong <menglong8.dong@xxxxxxxxx>
Date: Thu, 12 May 2022 15:16:13 +0800
Yeah, WLC and MH are excellent schedulers. As for SH, my fellows' feedback says that it doesn't work well. In fact, it's their fault, they just forget to enable port hash and just use the default ip
/html/lvs-devel/2022-05/msg00008.html (19,065 bytes)

4. Re: [PATCH net-next v2] net: ipvs: randomize starting destination of RR/WRR scheduler (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Wed, 11 May 2022 00:51:21 +0300 (EEST)
Hello, More time I spend on this topic, I'm less convinced that it is worth the effort. Randomness can come from another place: client address/port. Schedulers like MH and SH probably can help for su
/html/lvs-devel/2022-05/msg00007.html (16,892 bytes)

5. [PATCH net-next v2] net: ipvs: randomize starting destination of RR/WRR scheduler (score: 1)
Author: menglong8.dong@xxxxxxxxx
Date: Tue, 10 May 2022 15:43:01 +0800
For now, the start of the RR/WRR scheduler is in order of added destinations, it will result in imbalance if the director is local to the clients and the number of connection is small. For example, w
/html/lvs-devel/2022-05/msg00005.html (14,537 bytes)


This search system is powered by Namazu