mirror of
https://github.com/openvswitch/ovs
synced 2025-08-31 22:35:15 +00:00
faq: Specify QoS support is dependent on interface type.
QoS support depends on interface type; document it. Signed-off-by: Darrell Ball <dlu998@gmail.com> Signed-off-by: Ben Pfaff <blp@ovn.org>
This commit is contained in:
@@ -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
|
* Only a limited set of flow fields is modifiable via the set action by the
|
||||||
Hyper-V datapath.
|
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
|
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
|
vSwitch user, e.g. because their absence can be hidden by the ofproto layer
|
||||||
(usually this comes with a performance penalty).
|
(usually this comes with a performance penalty).
|
||||||
|
Reference in New Issue
Block a user