[ovs-discuss] ovs and tc's ingress qdisc

Wolfgang Bumiller w.bumiller at proxmox.com
Fri Sep 30 12:33:21 UTC 2016


I've noticed openvswitch apparently blindly deletes the ingress qdisc
of bridge ports even if no ingress policing is configured.
This also prevents the use of this qdisc for purposes other than the
in OVS implemented ingress policing (eg. handling fw-marks, bpf based
filters, or early port/address/mac filtering can be convenient at this
stage). Reading the source code didn't reveal any option to prevent
the qdisc from staying completely unmanaged, which would be the
simplest solution here.

What are your thoughts on this?

Much of the configuration variable handling code seems auto generated
and I'm unsure whether there's a good/simple way to distinguish
explicitly defined values from defaults. And considering all OVS does
for ingress policing is setting up 'tc' it seems it would make sense
to allow users to handle tc themselves, too.




More information about the discuss mailing list