Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/3\]\s+IPVS\:\s+add\s+wlib\s+\&\s+wlip\s+schedulers\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+1\/3\]\s+IPVS\:\s+add\s+wlib\s+\&\s+wlip\s+schedulers\s*$/: 4 ]

Total 4 documents matching your query.

1. Re: [PATCH 1/3] IPVS: add wlib & wlip schedulers (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Tue, 27 Jan 2015 10:36:34 +0200 (EET); Hello, For now I don't see hope in using schedulers that rely on IPVS byte/packet stats, due to the slow update (2 seconds). If we reduce this period we can cause performance problems to other users.; /html/lvs-devel/2015-01/msg00022.html (13,713 bytes)
2. Re: [PATCH 1/3] IPVS: add wlib & wlip schedulers (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Fri, 23 Jan 2015 00:06:12 +0200 (EET); Hello, All other schedulers react and see different picture after every new connection. The worst example is WLC where slow-start mechanism is desired because idle server can be overloaded before the; /html/lvs-devel/2015-01/msg00021.html (13,776 bytes)
3. Re: [PATCH 1/3] IPVS: add wlib & wlip schedulers (score: 1): Author: Chris Caputo <ccaputo@xxxxxxx>; Date: Fri, 23 Jan 2015 04:16:47 +0000 (UTC); This is exactly why my wlib/wlip code is a hybrid of wlc and rr. Last location is saved, and search is started after it. Thus when traffic is zero, round-robin occurs. When flows already exist, burst; /html/lvs-devel/2015-01/msg00020.html (14,889 bytes)
4. [PATCH 1/3] IPVS: add wlib & wlip schedulers (score: 1): Author: Chris Caputo <ccaputo@xxxxxxx>; Date: Tue, 20 Jan 2015 23:21:18 +0000 (UTC); Hi Julian, Thanks for the review. My application consists of incoming TCP streams being load balanced to servers which receive the feeds. These are long lived multi-gigabyte streams, and so I believe; /html/lvs-devel/2015-01/msg00015.html (15,669 bytes)

Current List: 1 - 4
Page: [1]