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 my driver getting called. Any clue/hint. I did below based on https://www.youtube.com/watch?v=15jgDWvH1Uo .

Thanks,
Ratheesh

ethtool -K eth0 ntuple off
ethtool -K eth0 hw-tc-offload on

ethtool -K sdp1-0  ntuple off
ethtool -K sdp1-0  hw-tc-offload on


ovs-vsctl set Open_vSwitch . other_config:tc-policy=skip_sw
 ovs-vsctl set Open_vSwitch . other_config:hw-offload=true

root@localhost:~/essential# ovs-vsctl show
90a6bd0c-f371-4471-8779-a33f91cff039
    Bridge "br0"
        Port "sdp1-0"
            Interface "sdp1-0"
        Port "br0"
            Interface "br0"
                type: internal
        Port "eth0"
            Interface "eth0"
    ovs_version: "2.5.9"


I could see that ping is successful.


root@localhost:~/essential# ovs-ofctl dump-flows br0
NXST_FLOW reply (xid=0x4):
cookie=0x0, duration=16.908s, table=0, n_packets=14, n_bytes=1334, idle_age=1, in_port=1 actions=output:2 cookie=0x0, duration=12.672s, table=0, n_packets=14, n_bytes=1334, idle_age=1, in_port=2 actions=output:1

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
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to