Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+v2\]\s+ipvs\:\s+drop\s+first\s+packet\s+to\s+dead\s+server\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH v2] ipvs: drop first packet to dead server (score: 1)
Author: Jiri Bohac <jbohac@xxxxxxx>
Date: Fri, 9 Oct 2015 18:17:34 +0200
Hi, right, good point! I tested this part; we found the problem on an old (3.12) kernel, we're missing the parts dealing with rescheduling on port reuse - only dealing with the "weight == 0" case. Lo
/html/lvs-devel/2015-10/msg00063.html (12,009 bytes)

2. Re: [PATCH v2] ipvs: drop first packet to dead server (score: 1)
Author: Julian Anastasov <ja@xxxxxx>
Date: Sun, 27 Sep 2015 20:25:18 +0300 (EEST)
Hello, So, at this point we do not know whether we have one or many real servers, with same or different forwarding method. For example, if we know that old real server is DR and the new real server
/html/lvs-devel/2015-09/msg00301.html (13,267 bytes)

3. [PATCH v2] ipvs: drop first packet to dead server (score: 1)
Author: Jiri Bohac <jbohac@xxxxxxx>
Date: Fri, 25 Sep 2015 11:48:20 +0200
[ original diff was against and older tree, sorry; rediffed against net-next ] Since commit dc7b3eb9 (ipvs: Fix reuse connection if real server is dead), new connections to dead servers are redistrib
/html/lvs-devel/2015-09/msg00300.html (9,835 bytes)


This search system is powered by Namazu