When one flow replaces another, traffic follows the old flow or the new one.
On Tue, Sep 27, 2016 at 12:31:34PM +0200, Andreas Gilbert wrote: > Hi Ben > > Thank you, exactly what i expected > So the traffic will not take another matching flow by adding the same flow > twice.. > > BR > Andreas > > 2016-09-26 17:02 GMT+02:00 Ben Pfaff <b...@ovn.org>: > > > On Mon, Sep 26, 2016 at 10:07:11AM +0200, Andreas Gilbert wrote: > > > From OpenFlow Specification 1.3: > > > > > > "If a flow entry with identical match fields and priority already resides > > > in the requested table, > > > then that entry, including its duration, must be cleared from the table, > > > and the new flow entry added." > > > > > > What does this mean for a traffic (stream) currently using such a flow ? > > > Will the flow be unavailable for short time during clear/insert, or is > > this > > > done atomically > > > (so may the traffic will use another suitable flow in the table) ? > > > For a test, add same flow every x seconds during a stream transfer... > > > > > > In general: when there is a flow table update, > > > the incoming traffic will be processed in parallel or will be halted > > until > > > table modification is finished ? > > > > OVS makes atomic changes to the flow table. > > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
