diff mbox series

[ovs-dev,v1] faq: Specify QoS support is dependent on interface type.

Message ID 1541786836-21768-1-git-send-email-dlu998@gmail.com
State Accepted
Headers show
Series [ovs-dev,v1] faq: Specify QoS support is dependent on interface type. | expand

Commit Message

Darrell Ball Nov. 9, 2018, 6:07 p.m. UTC
QoS support depends on interface type; document it.

Signed-off-by: Darrell Ball <dlu998@gmail.com>
---
 Documentation/faq/releases.rst | 4 ++++
 1 file changed, 4 insertions(+)

Comments

Ben Pfaff Nov. 9, 2018, 9:07 p.m. UTC | #1
On Fri, Nov 09, 2018 at 10:07:16AM -0800, Darrell Ball wrote:
> QoS support depends on interface type; document it.
> 
> Signed-off-by: Darrell Ball <dlu998@gmail.com>

Thanks, applied to master.
diff mbox series

Patch

diff --git a/Documentation/faq/releases.rst b/Documentation/faq/releases.rst
index 17d66fc..e7ca8c3 100644
--- a/Documentation/faq/releases.rst
+++ b/Documentation/faq/releases.rst
@@ -133,6 +133,10 @@  Q: Are all features available with all datapaths?
     * Only a limited set of flow fields is modifiable via the set action by the
       Hyper-V datapath.
 
+    * Userspace datapath support, in some cases, is dependent on the associated
+      interface types.  For example, DPDK interfaces support ingress and egress
+      policing, but not shaping.
+
     The following table lists features that do not *directly* impact an Open
     vSwitch user, e.g. because their absence can be hidden by the ofproto layer
     (usually this comes with a performance penalty).