I see.. let's wait if someone from OVS team joins the discussion.. :) > > Alright, so with a regular TAP, outside of OVS reach I get the following > for the above input: > > # tc class show dev vnet0 > class htb 1:1 root leaf 2: prio 0 rate 102400Kbit ceil 102400Kbit burst 1587b > cburst 1587b > > # tc filter show dev vnet0 ingress > filter parent ffff: protocol all pref 49152 u32 chain 0 > filter parent ffff: protocol all pref 49152 u32 chain 0 fh 800: ht divisor 1 > filter parent ffff: protocol all pref 49152 u32 chain 0 fh 800::800 order > 2048 key ht 800 bkt 0 flowid :1 not_in_hw > match 00000000/00000000 at 0 > police 0x2 rate 102400Kbit burst 12800Kb mtu 64Kb action drop overhead 0b > ref 1 bind 1 > > And 102400Kbit = 12800KiB which is the input value. Therefore, what we > really need here is confirmation from OVS team about the units for QoS. > Unfortunately, it's NOT documented (I don't quite understand why). > > I've found an example here [1] where to limit ingress at 10Mbps they > suggest: > > ovs-vsctl set interface vif1.0 ingress_policing_rate=10000 > > which means that the unit for ingress_policing_rate is kbps. Therefore, > 12800KiB/s (your input) times 8 (bits in byte) = 102400 (kbit/s) which > is what libvirt generates. So why OVS configures something else? > > If only there was a way to tell OVS to not clear QoS set from outside, > we could avoid this regression. But there isn't. > > 1: https://docs.openvswitch.org/en/latest/faq/qos/ > > Michal >
-- ------------------------------------- Ing. Nikola CIPRICH LinuxBox.cz, s.r.o. 28.rijna 168, 709 00 Ostrava tel.: +420 591 166 214 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: ser...@linuxbox.cz ------------------------------------- _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
