Reviewed: https://review.opendev.org/c/openstack/neutron-lib/+/860761
Committed:
https://opendev.org/openstack/neutron-lib/commit/99ba3d8b3f8fa94b7114cb8ba114d6d2fda7d683
Submitter: "Zuul (22348)"
Branch: master
commit 99ba3d8b3f8fa94b7114cb8ba114d6d2fda7d683
Author: LIU Yulong <i...@liuyulong.me>
Date: Sat Oct 8 15:49:54 2022 +0800
Add bandwidth rate limit table
This new table is used to implement QoS bandwidth limitation
by leveraging ovs meter.
Closes-Bug: #1964342
Change-Id: I87da4960a92bb807203534965bac2b0a42c5d4a4
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1964342
Title:
[QoS][OvS] implement QoS bandwidth limitation by leveraging ovs meter
Status in neutron:
Fix Released
Bug description:
We are going to implement packet rate limit on ovs bridge by using
meter rules [1], at the same time, meter can also be used to limit the
bandwidth. os-key(ryu) supports the rule types of OFPMF_KBPS [2]. And
usually, some smart-NICs for ovs offloading will support offloading
meter rule to NIC to save the QoS cost of CPU on hosts naturally.
Since TC rules can be offloaded to smart-NIC as well. So this is an
alternative to make the implementation of QoS limitation in a
consistent mechanism.
thought?
[1]
https://review.opendev.org/c/openstack/neutron/+/816800/8/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/br_int.py
[2]
https://ryu.readthedocs.io/en/latest/ofproto_v1_3_ref.html#ryu.ofproto.ofproto_v1_3_parser.OFPMeterMod
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1964342/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
