Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFC\]\s+IPVS\:\s+secure_tcp\s+does\s+provide\s+alternate\s+state\s+timeouts\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFC\]\s+IPVS\:\s+secure_tcp\s+does\s+provide\s+alternate\s+state\s+timeouts\s*$/: 3 ]

Total 3 documents matching your query.

1. Re: [RFC] IPVS: secure_tcp does provide alternate state timeouts (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Thu, 29 Sep 2011 18:01:56 +0900; Yes, I agree there is room for improvement. I guess the best way forward is to use netlink to allow per-state per-protocol timeout adjustment. In the mean time, I'll queue this patch up as I think it; /html/lvs-devel/2011-09/msg00032.html (12,148 bytes)
2. Re: [RFC] IPVS: secure_tcp does provide alternate state timeouts (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Thu, 29 Sep 2011 11:47:10 +0300 (EEST); Hello, Yes, only states are changed. What is missing is a libipvs support to modify per-protocol timeouts because they are not exported to /proc anymore. As the states have name, may be we can implem; /html/lvs-devel/2011-09/msg00031.html (11,154 bytes)
3. [RFC] IPVS: secure_tcp does provide alternate state timeouts (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Thu, 29 Sep 2011 16:25:11 +0900; * Also reword the test to make it read more easily (to me) Signed-off-by: Simon Horman <horms@xxxxxxxxxxxx> -- Julian, I don't see that IPVS currently implements alternate timeouts for secure_tcp. Am; /html/lvs-devel/2011-09/msg00029.html (10,245 bytes)

Current List: 1 - 3
Page: [1]