On 16 Nov 2024, at 8:05, Rama Chaitanya Kandula via discuss wrote:
> Hi Team members, > > We are trying to experiment the TC qdisc behaviour with hw-offload > enabled(Kernel offload using TC). Need clarification on below queries. > > > 1. As part of HW Offload being enabled on OVS (using ovs-vsctl set > Open_vSwitch . other_config:hw-offload=true), we are observing that the TC > INGRESS QDISC is always getting created by OVS on addition of tap to bridge. > Please can you help us in understanding why this is being added to all the > ports which are participating in the bridge ? Our understanding is that > virtual port like tap won’t be participate in HW offload. When hardware offload for the kernel is enabled by default all port (even the non-hardware offload capable ones) will use TC for datapath handling. If a flow is not supported by TC it will fall back to the kernel module. > 2. We also wanted to understand the reason behind keeping the TC INGRESS > QDISC creation as Exclusive flag. We are trying to supplement this with > another qdisc (tc qdisc add dev tap0 clsact) but the creation itself is > failing since the current INGRESS qdisc is kept with Exclusivity flag turned > on. Not sure why we chose to set this flag. I assume to avoid people from tampering with the OVS applied configuration. > > Thanks in advance, > Rama Chaitanya > _______________________________________________ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
