DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jasvinder Singh <jasvinder.singh@intel.com>
To: dev@dpdk.org
Cc: cristian.dumitrescu@intel.com, john.mcnamara@intel.com,
	marko.kovacevic@intel.com, thomas@monjalon.net
Subject: [dpdk-dev] [PATCH v2 3/3] examples/ip_pipeline: documentation update
Date: Tue, 26 Nov 2019 14:28:31 +0000	[thread overview]
Message-ID: <20191126142831.55017-3-jasvinder.singh@intel.com> (raw)
In-Reply-To: <20191126142831.55017-1-jasvinder.singh@intel.com>

Updates documentation for traffic manager cli as per the changes
made to qos scheduler library.

Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
---
 doc/guides/sample_app_ug/ip_pipeline.rst | 24 ++++++++++++++++--------
 1 file changed, 16 insertions(+), 8 deletions(-)

diff --git a/doc/guides/sample_app_ug/ip_pipeline.rst b/doc/guides/sample_app_ug/ip_pipeline.rst
index 4da0fcf89..56014be17 100644
--- a/doc/guides/sample_app_ug/ip_pipeline.rst
+++ b/doc/guides/sample_app_ug/ip_pipeline.rst
@@ -249,27 +249,35 @@ Traffic manager
 
   tmgr subport profile
    <tb_rate> <tb_size>
-   <tc0_rate> <tc1_rate> <tc2_rate> <tc3_rate>
+   <tc0_rate> <tc1_rate> <tc2_rate> <tc3_rate> <tc4_rate>
+   <tc5_rate> <tc6_rate> <tc7_rate> <tc8_rate>
+   <tc9_rate> <tc10_rate> <tc11_rate> <tc12_rate>
    <tc_period>
-
+   pps <n_pipes_per_subport>
+   qsize <qsize_tc0> <qsize_tc1> <qsize_tc2>
+   <qsize_tc3> <qsize_tc4> <qsize_tc5> <qsize_tc6>
+   <qsize_tc7> <qsize_tc8> <qsize_tc9> <qsize_tc10>
+   <qsize_tc11> <qsize_tc12>
 
  Add traffic manager pipe profile ::
 
   tmgr pipe profile
    <tb_rate> <tb_size>
-   <tc0_rate> <tc1_rate> <tc2_rate> <tc3_rate>
+   <tc0_rate> <tc1_rate> <tc2_rate> <tc3_rate> <tc4_rate>
+   <tc5_rate> <tc6_rate> <tc7_rate> <tc8_rate>
+   <tc9_rate> <tc10_rate> <tc11_rate> <tc12_rate>
    <tc_period>
-   <tc_ov_weight> <wrr_weight0..15>
+   <tc_ov_weight>
+   <wrr_weight0..3>
 
  Create traffic manager port ::
 
   tmgr <tmgr_name>
    rate <rate>
    spp <n_subports_per_port>
-   pps <n_pipes_per_subport>
-   qsize <qsize_tc0>
-   <qsize_tc1> <qsize_tc2> <qsize_tc3>
-   fo <frame_overhead> mtu <mtu> cpu <cpu_id>
+   fo <frame_overhead>
+   mtu <mtu>
+   cpu <cpu_id>
 
  Configure traffic manager subport ::
 
-- 
2.21.0


  parent reply	other threads:[~2019-11-26 13:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 13:19 [dpdk-dev] [PATCH 1/3] sched: " Jasvinder Singh
2019-10-29 13:19 ` [dpdk-dev] [PATCH 2/3] examples/qos_sched: " Jasvinder Singh
2019-11-04 10:29   ` Dumitrescu, Cristian
2019-10-29 13:19 ` [dpdk-dev] [PATCH 3/3] examples/ip_pipeline: " Jasvinder Singh
2019-11-04 10:29   ` Dumitrescu, Cristian
2019-11-04 10:30 ` [dpdk-dev] [PATCH 1/3] sched: " Dumitrescu, Cristian
2019-11-26  8:47 ` Thomas Monjalon
2019-11-26  9:16 ` Thomas Monjalon
2019-11-26  9:55   ` Singh, Jasvinder
2019-11-26 14:28 ` [dpdk-dev] [PATCH v2 " Jasvinder Singh
2019-11-26 14:28   ` [dpdk-dev] [PATCH v2 2/3] examples/qos_sched: " Jasvinder Singh
2019-11-26 14:28   ` Jasvinder Singh [this message]
2019-11-26 15:22   ` [dpdk-dev] [PATCH v2 1/3] sched: " Thomas Monjalon

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=20191126142831.55017-3-jasvinder.singh@intel.com \
    --to=jasvinder.singh@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=thomas@monjalon.net \
    /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).