From a17d97fc00d7467e9128f9691d3409636ce1e9b4 Mon Sep 17 00:00:00 2001 From: Miguel Angel Ajo Date: Tue, 11 Aug 2015 16:47:23 +0200 Subject: [PATCH] Update documentation acording to last QoS/OvS changes Change Ie802a235ae19bf679ba638563ac7377337448f2a introduces a few changes to the low level ovs implementation of QoS, this patch updates documentation. Change-Id: I46a972b045c03f65888a22f55e893c69da3db14b Partially-Implements: ml2-qos --- doc/source/devref/quality_of_service.rst | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/doc/source/devref/quality_of_service.rst b/doc/source/devref/quality_of_service.rst index 87b6999dc..3a4d6f3c9 100644 --- a/doc/source/devref/quality_of_service.rst +++ b/doc/source/devref/quality_of_service.rst @@ -262,20 +262,17 @@ Open vSwitch Open vSwitch implementation relies on the new ovs_lib OVSBridge functions: -* create_qos_bw_limit_for_port -* get_qos_bw_limit_for_port -* del_qos_bw_limit_for_port +* get_egress_bw_limit_for_port +* create_egress_bw_limit_for_port +* delete_egress_bw_limit_for_port -An egress bandwidth limit is effectively configured on the port by creating a -single QoS queue with min-rate=rule.max_kbps, max-rate=rule.max_kbps and -burst=rule.max_burst_kbps. Then a linux-htb QoS policy is defined on the port, -attached to the queue. - -HTB queues are supported at least in all 2.x versions of Open vSwitch. - -More details about HTB in `the blog post -`_. +An egress bandwidth limit is effectively configured on the port by setting +the port Interface parameters ingress_policing_rate and +ingress_policing_burst. +That approach is less flexible than linux-htb, Queues and OvS QoS profiles, +which we may explore in the future, but which will need to be used in +combination with openflow rules. Configuration ============= -- 2.45.2