doc/tm: update support for pf only

Message ID 20181015074648.35861-1-vipin.varghese@intel.com (mailing list archive)
State Not Applicable, archived
Headers
Series doc/tm: update support for pf only |

Checks

Context Check Description
ci/Intel-compilation success Compilation OK
ci/checkpatch success coding style OK

Commit Message

Varghese, Vipin Oct. 15, 2018, 7:46 a.m. UTC
  Documentation is updated to highlight the support for DPDK ethernet
interface for Traffic Manager is currently limited to PF only.

Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
 doc/guides/prog_guide/traffic_management.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
  

Patch

diff --git a/doc/guides/prog_guide/traffic_management.rst b/doc/guides/prog_guide/traffic_management.rst
index 98ac4310b..e6304d372 100644
--- a/doc/guides/prog_guide/traffic_management.rst
+++ b/doc/guides/prog_guide/traffic_management.rst
@@ -16,7 +16,8 @@  is agnostic of the underlying HW, SW or mixed HW-SW implementation.
 Main features:
 
 * Part of DPDK rte_ethdev API
-* Capability query API per port, per hierarchy level and per hierarchy node
+* Capability query API per port, per hierarchy level and per hierarchy node on
+  PF ethernet devices
 * Scheduling algorithms: Strict Priority (SP), Weighed Fair Queuing (WFQ)
 * Traffic shaping: single/dual rate, private (per node) and
   shared (by multiple nodes) shapers
@@ -221,3 +222,4 @@  thus operations such as node add/delete, node suspend/resume, parent node
 update, etc., can be invoked after the Ethernet port has been started, subject
 to the specific implementation supporting them. The set of dynamic updates
 supported by the implementation is advertised through the port capability set.
+TM features are currently supported for PF Ethernet devices.