On 30.01.24 10:44, Simon Horman wrote: > On Fri, Jan 26, 2024 at 02:24:51PM +0100, [email protected] wrote: >> From: Jakob Meng <[email protected]> >> >> In a scenario where OVN does load balancing and then SNAT with a OVS >> userspace datapath [0], the recirc_depth may be greater than 6. In >> that case, ovs-vswitchd might drop packets and raise warnings: >> >> dpif_netdev|WARN|Packet dropped. Max recirculation depth exceeded. >> >> Increasing MAX_RECIRC_DEPTH to 8 solves this issue. >> >> [0] >> https://github.com/ovn-org/ovn/blob/dd5cd73e3df1bfb1a215cb45d1e2e03eff1d049a/tests/system-ovn-kmod.at#L740 >> >> Reported-at: https://issues.redhat.com/browse/FDP-251 >> Signed-off-by: Jakob Meng <[email protected]> > Hi Jakob, > > I'm unsure what the considerations were when setting this limit, > but I do note that it was increased once before, from 5 to 6, > for an OVN use-case [1]. So this approach seems reasonable to me. > > Acked-by: Simon Horman <[email protected]> > > [1] dpif-netdev: Set MAX_RECIRC_DEPTH to 6. > https://github.com/openvswitch/ovs/commit/3f9d3836d63a >
Hi Ilya, can we include this patch in 3.3, please? It is required for more complex setups like OKD/OpenShift with userspace datapaths. Best, Jakob _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
