Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+netfilter\:\s+ipvs\:\s+Add\s+Maglev\s+consistent\s+hashing\s+scheduler\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+netfilter\:\s+ipvs\:\s+Add\s+Maglev\s+consistent\s+hashing\s+scheduler\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH] netfilter: ipvs: Add Maglev consistent hashing scheduler (score: 1): Author: Inju Song <inju.song@xxxxxxxxxxxxx>; Date: Tue, 21 Nov 2017 01:36:08 +0900; Hello, Julian Thank you for your a lot of comments. I agree. In this case, weight value is same weight or zero. So I will consider this case when I patch the source. I have read your comments about m; /html/lvs-devel/2017-11/msg00019.html (15,158 bytes)
2. Re: [PATCH] netfilter: ipvs: Add Maglev consistent hashing scheduler (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sun, 19 Nov 2017 18:04:35 +0200 (EET); Hello, I see that the PDF shows implementation only for servers with same weight. It would be better to see implementation that considers dest->weight. While calling del_dest svc->num_dests can be 0,; /html/lvs-devel/2017-11/msg00018.html (13,302 bytes)
3. [PATCH] netfilter: ipvs: Add Maglev consistent hashing scheduler (score: 1): Author: Inju Song <inju.song@xxxxxxxxxxxxx>; Date: Sun, 19 Nov 2017 15:35:13 +0900; Implements the Google's Maglev hashing algorithm as a IPVS scheduler. Basically it provides consistent hashing but offers some special features about disruption and load balancing. 1) minimal disrupt; /html/lvs-devel/2017-11/msg00017.html (23,500 bytes)

Current List: 1 - 3
Page: [1]