On Jan 18, 2016, at 11:05 AM, Victor J. Orlikowski <[email protected]<mailto:[email protected]>> wrote:
The reason for this is - without *something* to keep track of datapaths that have made it through handshaking, we cannot make any reasonable attempt to clean up datapath objects that have *not* made it through handshaking, but for which the socket connection was interrupted without receiving a FIN or RST (meaning, the socket connection for the datapath is still in ESTABLISHED state). The *only* way to do this is to force closure of any datapath (and associated socket/greenlets) that has not successfully registered itself with a topology or dpset object. I came up with a way around the above (requiring the use of dpset or topology for any application that needed cleanup). In effect, applications need to keep track of what datapaths they use. Once they have done so, they should set the “assured” attribute on the datapath in question. This change required wide-ranging cleanup in the source tree, which included topology, so I wrapped it all into one patch. Apply the attached stability patch against a clean Ryu 3.29, and let me know how it treats you. Best, Victor -- Victor J. Orlikowski <> vjo@[cs.]duke.edu<http://duke.edu>
stability.patch
Description: stability.patch
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
