> 2023年4月7日 下午5:01，Chengcheng Luo <chengcheng....@smartx.com> 写道：
>
> Hi .
> I am using ovs-2.13.3, and I have configured QoS with the following
> parameters: min-rate = 200Mbps max-rate = 500Mbps burst = 10Mb
> The QoS queue configuration in ovsdb is normal, as shown below:
> [root@l]$ovs-vsctl list queue b7ca3e81-3672-41b7-a0d0-12368d39816e
> _uuid : b7ca3e81-3672-41b7-a0d0-12368d39816e
> dscp : []
> external_ids : {}
> other_config : {burst="10000000", max-rate="250000000.0",
> min-rate="100000000.0", priority="100"}
> The corresponding tc_class is as follows:
> tc class show dev enp4s0f0
> class htb 1:b2 parent 1:fffe prio 7 rate 12000bit ceil 20000Mbit burst 1563b
> cburst 0b
> The QoS configuration as seen in ovs-appctl qos/show enp4s0f0 is as follows:
> Queue 177: burst: 10000000 priority: 100 min-rate: 12000 max-rate:
> 20000000000 tx_packets: 0 tx_bytes: 0 tx_errors: 0
>
As you can see, the ovs-appctl and tc class configurations are inconsistent
with the QoS queue configuration in ovsdb, causing the QoS settings to not take
effect.
Does this seem like a bug in the OVS implementation?
> Echken
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
