On 22 Sep 2025, at 9:19, Ratheesh Kannoth wrote:
> From: Eelco Chaudron <[email protected]> > Sent: Monday, September 22, 2025 12:34 PM > To: Ratheesh Kannoth <[email protected]> > Cc: [email protected]; Simon Horman <[email protected]> > Subject: Re: [ovs-discuss] OVS offload > >> On 19 Sep 2025, at 12: 14, Ratheesh Kannoth via discuss wrote: Hi, I did >> following configuration; but did not see .ndo_setup_tc() of > > >> You could use the -m option to check if the flows are offloaded. However, >> your ingress and egress port need to be on the same nic (you might need to >> setup a vf). >> If you leave the tc-policy to default, it should at least install the tc >> flows, and then you can see if they are in hw or not. >> //Eelco > > Thanks, when I changed the ovs version to 3.6.0, flows gets offloaded. I > could see that “ovs-appctl dpctl/dump-flows -m type=offloaded”. But now > stats sync are not getting called. I added > Prints in netdev_tc_flow_get() and figured out that it is not hitting. So > flow gets deleted by netdev_tc_flow_del() after some time. When I used > "ovs-vsctl set Open_vSwitch . other_config:max-idle=30000" command to > to increase the idle time flow delete takes a little more time. See my reply to your other email, check the tc command to see if the counters get incremented by the driver. OVS gets the counters roughly every 500ms as part of the revalidator process (see the https://developers.redhat.com/articles/2022/10/19/open-vswitch-revalidator-process-explained blog if you want to learn more). //Eelco _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
