Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
configure qos linux-htb policy, and found the it does not work for dpdk case
Version-Release number of selected component (if applicable):
dpdk-17.11-7.el7.x86_64.rpm
dpdk-tools-17.11-7.el7.x86_64.rpm
openvswitch-2.9.0-55.el7fdp.x86_64.rpm
How reproducible:
Steps to Reproduce:
1. Add ovs bridge
ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev
2. Add dpdk0 port to ovs bridge
ovs-vsctl add-port ovsbr0 dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs=0000:04:00.0
3. Add two guest port to ovs bridge
ovs-vsctl add-port ovsbr0 vhost0 -- set interface vhost0 type=dpdkvhostuser ofport_request=5
ovs-vsctl add-port ovsbr0 vhost1 -- set interface vhost1 type=dpdkvhostuser ofport_request=6
4. Configure the htb policy on the guest port
ovs-vsctl set port dpdk0 qos=@newqos -- --id=@newqos create qos type=linux-htb other-config:max-rate=200000000 other-config:min-rate=100000000 queues:123=@vhost0queue queues:234=@vhost1queue -- --id=@vhost0queue create queue other-config:max-rate=20000000 other-config:min-rate=10000000 -- --id=@vhost1queue create queue other-config:max-rate=40000000 other-config:min-rate=20000000
5. Configure the openflow
ovs-ofctl add-flow ovsbr0 in_port=5,actions=set_queue:123,normal
ovs-ofctl add-flow ovsbr0 in_port=6,actions=set_queue:234,normal
ovs-ofctl add-flow ovsbr0 actions=NORMAL
6. start guest1 and guest2.
guest1 start netperf server, guest2 do the netperf testing.
Actual results:
When enable linux-htb policy on dpdk0, the result was same with without linux-htb policy.
Expected results:
The linux-htb policy should work for ovs dpdk case.max-rate, min-rate should be take effect.
Additional info: