From: Vipin Varghese <vipin.varghese@intel.com>
To: dev@dpdk.org, jingjing.wu@intel.com, wenzhuo.lu@intel.com,
bernard.iremonger@intel.com
Cc: stephen1.byrne@intel.com, Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH] doc/tm: update support for pf only
Date: Mon, 15 Oct 2018 13:16:48 +0530 [thread overview]
Message-ID: <20181015074648.35861-1-vipin.varghese@intel.com> (raw)
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(-)
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.
--
2.17.1
next reply other threads:[~2018-10-15 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 7:46 Vipin Varghese [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-15 7:04 Vipin Varghese
2018-10-15 15:34 ` Jerin Jacob
2018-10-15 15:52 ` Dumitrescu, Cristian
2018-10-15 15:52 ` Dumitrescu, Cristian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181015074648.35861-1-vipin.varghese@intel.com \
--to=vipin.varghese@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=stephen1.byrne@intel.com \
--cc=wenzhuo.lu@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).