On 4/25/23 20:36, Lorenzo Bianconi wrote: > Rework OVN QoS implementation in order to configure it through OVS QoS > table instead of running tc command directly bypassing OVS.
Hi, Lorenzo. One question: Does this patch set impact the behavior around custom qdiscs applied externally? For example, if something like libvirt sets qdisc for a port before this port is attached to OVS, OVS will remove it, unless qos_type is set to linux-noop. And OVS will remove the existing qdisc and set up a new one if the qos_type is set to some other value. Does this patch set change anything in regards to this behavior? i.e. what would be the end result of adding a port with a custom qdisc to OVS/OVN if QoS is not configured in OVN ? Will qdisc be removed or will it stay? And is it the same behavior as it was before that patch set? Also, in case OpenStack sets qos type to linux-noop before adding port to OVS, will OVN clear that value? Asking because having a custom 'noqueue' qdisc for tap interfaces is desirable for performance reasons. Libvirt creates it and OpenStack may set the linux-noop QoS type in OVS in order to preserve this custom qdisc. Best regards, Ilya Maximets. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
