From: Rosen Xu <rosen.xu@intel.com>
To: dev@dpdk.org
Cc: cristian.dumitrescu@intel.com, wenzhuo.lu@intel.com,
jasvinder.singh@intel.com, rosen.xu@intel.com,
ferruh.yigit@intel.com
Subject: [dpdk-dev] [PATCH v2 0/2] Add and identify shaper profile parameters
Date: Mon, 22 Oct 2018 16:46:39 +0800 [thread overview]
Message-ID: <1540198001-127116-1-git-send-email-rosen.xu@intel.com> (raw)
In-Reply-To: <1534156498-57837-1-git-send-email-rosen.xu@intel.com>
v2 updates:
==========
- Updated commmand section
- Updated the documentation
v1 updates:
==========
- Added committed and peak parameters
As struct rte_tm_shaper_params defined, the command line of
test-pmd should include committed and peak parameters, but
right now the command line doesn't identify whether it's
committed or peak parameter. This patch identifies and
adds the clarify definition. This patch also update command
section and the documentation.
Rosen Xu (2):
app/test-pmd: add and identify shaper profile parameters
doc/guides/testpmd_app_ug: update documentation for added shaper
profile parameters
app/test-pmd/cmdline.c | 3 ++-
app/test-pmd/cmdline_tm.c | 34 ++++++++++++++++++++---------
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 9 +++++---
3 files changed, 32 insertions(+), 14 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2018-10-22 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 10:34 [dpdk-dev] [PATCH] app/test-pmd: add " Rosen Xu
2018-09-25 11:55 ` Singh, Jasvinder
2018-10-16 15:00 ` Dumitrescu, Cristian
2018-10-17 10:01 ` Xu, Rosen
2018-10-22 8:48 ` Xu, Rosen
2018-10-22 8:49 ` Xu, Rosen
2018-10-22 8:46 ` Rosen Xu [this message]
2018-10-22 8:46 ` [dpdk-dev] [PATCH v2 1/2] [PATCH v2 1/2] " Rosen Xu
2018-10-22 8:46 ` [dpdk-dev] [PATCH v2 2/2] [PATCH v2 2/2] doc/guides/testpmd_app_ug: update documentation for added " Rosen Xu
2018-10-22 12:28 ` Kovacevic, Marko
2018-10-22 9:34 ` [dpdk-dev] [PATCH v2 0/2] Add and identify " Singh, Jasvinder
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=1540198001-127116-1-git-send-email-rosen.xu@intel.com \
--to=rosen.xu@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@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).