Bug 1546429

Description of requirement:
OVS QoS
http://docs.openvswitch.org/en/latest/howto/qos/
http://docs.openvswitch.org/en/latest/faq/qos/#
OVS already supports ingress policing or rate limiting 

there is no support for queuing, basic token bucket and token bucket size is that of bust size; drop packets if rate exceeded, setting burst size allows algorithm to be more forgiving

For example, the following commands will rate-limit traffic that vif1.0 may generate to 10Mbps:

$ ovs-vsctl set interface vif1.0 ingress_policing_rate=10000 
$ ovs-vsctl set interface vif1.0 ingress_policing_burst=8000

OVS supports egress traffic shaping 
2 queuing options linux-htb or linux-hfsc
specify 
min-rate - Minimum guaranteed bandwidth, in bit/s. 
max rate - Maximum allowed bandwidth, in bit/s.

limit traffic from VM vif1.0 to physical outgoing port eth0 to min-rate 10 Mbps and max-rate 40Mbps; physical port eth0 supports max-rate of 1Gbps

ovs-vsctl -- set Port eth0 qos=@newqos -- \
--id=@newqos create qos type=linux-htb other-config:max-rate=1000000000 queues=0= -- \
--id= create queue other-config:min-rate=10000000 other-config:max-rate=40000000


OVS-DPDK has ingress policing similar to OVS
http://docs.openvswitch.org/en/latest/howto/dpdk/#qos

DPDK Egress policer for 1Mpps
$ ovs-vsctl set port vhost-user0 qos=@newqos -- \
    --id=@newqos create qos type=egress-policer other-config:cir=46000000 \
    other-config:cbs=2048`

Committed Information Rate (CIR) is measured in bytes of IP
              packets per second, i.e. it includes the IP header

SR-IOV VF min and max TX rate, supported with some NICs (Intel ixgbe and Mellanox mlx5)
Bug 1340914 - Add support to configure SR-IOV VF minimum and maximum Tx rate through ip tool (RHEL 7.3)
- TX rate must atleast achieve minimum bandwidth but should not exceed max bandwidth
SR-IOV VF max RX rate (policing) not currently supported
https://communities.intel.com/thread/117593

Benchmark ingress rate limiting for OVS and OVS-DPDK 
Test- 4 VMs each vif interface has a ingress rate limit defined of 10Mbps, 10Mbps 100Mbps, 100 Mbps respectively and burst=5Mb,
There is congestion, incoming traffic for each VM exceeds expected ingress rate by double
Verify each VM is receiving allocated rate

Benchmark egress traffic shaping for SR-IOV, OVS  
Test- 4 VMs each vif interface has egress traffic shaping defined; linux-htb or linux-hfsc  with min-rate 10Mbps and max-rate 40Mbps

Verify VMs are able to achieve minimum rate and don't exceed maximum rate
setup testpmd in guest with L2FWD and transmit 100Mbps per VM, verify traffic is shaped to match configuration above

Benchmark egress traffic shaping with egress-policer for OVS-DPDK
Test- 2 VMs each vif interface has egress-policer  for 1 Mpps with cir=46000000, cbs=2048
Verify each VM is able to CIR and minimum packet rate of 1Mpps
setup testpmd in guest with L2FWD and transmit 1.5Mpps per VM, verify traffic is shaped to match configuration above

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: