On Sat, Jan 23, 2016 at 02:05:54PM +0000, Jan Scheurich wrote: > Our hit-less resync proposal is not really about atomic updates to > flow tables. It is rather a generic, simple, and efficient way for an > SDN controller to ensure that the entire flow state (flows, groups, > meters) of a switch is re-aligned with the master state on the > controller, while continuing non-stop forwarding. A controller would > typically perform it after a local restart or a temporary connection > loss. > > The mentioned approaches for atomic updates of flow tables do not > really help in situations where a controller needs to resynchronize a > million of flow, group and meter entries. Our proposed method works > in-place on the OVS and does not require any extra resources other > than a generation field per entry. > > The procedure has been implemented and in use Ericsson's OVS vSwitch > and ODL controller for some time and we would like to upstream it both > to OVS and ODL now. We have a patch ready that we can submit for > review.
I don't see how the proposed feature is better than what we already have. It saves a little memory temporarily, but memory isn't usually a big deal in typical OVS environments. Is there some other advantage? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
