Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+ipvs\:\s+allow\s+rescheduling\s+of\s+new\s+connections\s+when\s+port\s+reuse\s+is\s+detected\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\]\s+ipvs\:\s+allow\s+rescheduling\s+of\s+new\s+connections\s+when\s+port\s+reuse\s+is\s+detected\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [PATCH] ipvs: allow rescheduling of new connections when port reuse is detected (score: 1): Author: Marcelo Ricardo Leitner <mleitner@xxxxxxxxxx>; Date: Mon, 23 Feb 2015 11:59:14 -0300; Hi, Took me a while to understand the memory leak it would be creating. Nice catch, thanks. Ok. Please let me know if I can do anything to help. Thanks, Marcelo -- To unsubscribe from this list: send; /html/lvs-devel/2015-02/msg00041.html (13,137 bytes)
2. Re: [PATCH] ipvs: allow rescheduling of new connections when port reuse is detected (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Sat, 21 Feb 2015 19:15:40 +0200 (EET); Hello, Just noticed that a small change is needed here. We have very odd handling of pe and pe_data. Can you change the code so that we here use: __ip_vs_conn_put(cp); kfree(param->pe_data); return;; /html/lvs-devel/2015-02/msg00036.html (12,385 bytes)
3. [PATCH] ipvs: allow rescheduling of new connections when port reuse is detected (score: 1): Author: Marcelo Ricardo Leitner <mleitner@xxxxxxxxxx>; Date: Fri, 20 Feb 2015 17:39:25 -0200; Currently, when TCP/SCTP port reusing happens, IPVS will find the old entry and use it for the new one, behaving like a forced persistence. But if you consider a cluster with a heavy load of small co; /html/lvs-devel/2015-02/msg00035.html (17,345 bytes)

Current List: 1 - 3
Page: [1]