From 28e07d4c5eb9eec0c51f0e6b055c8ded64bc2d13 Mon Sep 17 00:00:00 2001 From: Hongbin Lu Date: Thu, 16 Aug 2018 22:24:27 +0000 Subject: [PATCH] Doc: update the qos devref about SR-IOV support SR-IOV has added support for enforcing egress minimum bandwidth [1] and this commit updates the devref about that. [1] https://review.openstack.org/#/c/347302/ Change-Id: I0e637b893e60d7fdfb1ab4cece15aad74f43d3b5 Related-Bug: #1578989 --- doc/source/contributor/internals/quality_of_service.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/source/contributor/internals/quality_of_service.rst b/doc/source/contributor/internals/quality_of_service.rst index bd0fbf85e09..4252775f126 100644 --- a/doc/source/contributor/internals/quality_of_service.rst +++ b/doc/source/contributor/internals/quality_of_service.rst @@ -350,12 +350,15 @@ openflow rules. SR-IOV ++++++ -SR-IOV bandwidth limit implementation relies on the new pci_lib function: +SR-IOV bandwidth limit and minimum bandwidth implementation relies on the +new pci_lib function: -* set_vf_max_rate +* set_vf_rate As the name of the function suggests, the limit is applied on a Virtual -Function (VF). +Function (VF). This function has a parameter called "rate_type" and +its value can be set to "rate" or "min_tx_rate", which is for enforcing +bandwidth limit or minimum bandwidth respectively. ip link interface has the following limitation for bandwidth limit: it uses Mbps as units of bandwidth measurement, not kbps, and does not support float