On Tue, Jun 04, 2019 at 11:47:57AM +0000, Vishal Deep Ajmera wrote: > Current OVS implementation frees the ofport number allocated for > a given ofport if the underlying interface could not get initialized > due to any error. However it does not delete the entry of ofport from > ovsdb. This means any new ofport can get this ofport number anytime > in future. When the underlying interface issue is resolved for the > ofport it gets a new ofport number from the pool. This has an > undesired effect where any SDN controller will have to modify all the > flows pertaining this ofport due to change in ofport number and > reprogram the flows in the switch. > > This patch reserves the ofport port number for the duration the ofport > entry persists in the ovsdb. Once the entry is deleted from ovsdb the > ofport number is recirculated on LRU basis. > > Signed-off-by: Vishal Deep Ajmera <vishal.deep.ajm...@ericsson.com>
This is an interesting patch and I like the idea. The implementation does add some conceptual complexity. Can you say some more about the scenario that this covers? It isn't one that I've heard come up very much in the past. Does it arise in real situations that you've encountered? _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
