On 9/19/24 19:08, Lorenzo Bianconi wrote: > With respect to the previous implementation, OVN is now tracking and > flushing ECMP next-hop ct entries with the next-hop mac address instead > of using an identification number committed by ovn-northd since the previous > approach had some limitations when the traffic is initialized from outside > the ovn cluster. This series is introducing a way to periodically resolve L2 > address of the configured next-hops. > Please note IPv6 is not currently supported and it will be added before > posting > a formal series. The goal of this series is just to collect feedbacks about > the > proposed approach. > > Changes in v2: > - add IPv6 support > > Lorenzo Bianconi (4): > northd: Introduce ECMP_Nexthop table in SB db. > pinctrl: Send periodic arp/nd to ecmp next-hops. > pinctrl: Update ecmp-nexthop mac resolving L2 address. > ofctrl: Introduce ecmp_nexthop_monitor. >
Hi Lorenzo, Sorry for the delay in providing feedback on this RFC. I shared some comments on each of the patches. I only did a superficial review for now. The approach is probably OK as long as we don't expect a lot of ECMP static routes with lots of different next hops. Regards, Dumitru _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
