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

Total 1 documents matching your query.

1. [PATCH nf-next] ipvs: allow rescheduling of new connections when port reuse is detected (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Mon, 2 Mar 2015 11:39:23 +0900; 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-03/msg00001.html (17,771 bytes)

Current List: 1 - 1
Page: [1]