From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-tm 18.05 pre-rc3
Date: Tue, 8 May 2018 18:12:28 +0100 [thread overview]
Message-ID: <1525799548-163555-1-git-send-email-cristian.dumitrescu@intel.com> (raw)
The following changes since commit 211992f3b7df5d6d8f1dbefc48bc37a6d5398fbc:
examples/flow_classify: fix validation in port init (2018-04-30 15:48:26 +0200)
are available in the git repository at:
http://dpdk.org/git/next/dpdk-next-qos
for you to fetch changes up to 06e2b9d59f4e1d85b4131ea4ecd8b97371dee029:
app/testpmd: add command to resume a TM node (2018-05-04 15:40:42 +0100)
----------------------------------------------------------------
Ben Shelton (1):
ethdev: Fix issue in Doxygen for TM API
Jasvinder Singh (1):
librte_sched: add post-init pipe profile api
Nikhil Rao (1):
ethdev: add support for WRED thresholds in bytes
Tomasz Duszynski (2):
app/testpmd: add command to suspend a TM node
app/testpmd: add command to resume a TM node
app/test-pmd/cmdline.c | 8 +
app/test-pmd/cmdline_tm.c | 128 +++++++++++++++
app/test-pmd/cmdline_tm.h | 2 +
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 10 ++
drivers/net/softnic/rte_eth_softnic_tm.c | 23 ++-
lib/librte_ethdev/rte_tm.h | 55 ++++++-
lib/librte_sched/rte_sched.c | 239 ++++++++++++++++++----------
lib/librte_sched/rte_sched.h | 18 +++
lib/librte_sched/rte_sched_version.map | 6 +
9 files changed, 400 insertions(+), 89 deletions(-)
next reply other threads:[~2018-05-08 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 17:12 Cristian Dumitrescu [this message]
2018-05-10 0:10 ` 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=1525799548-163555-1-git-send-email-cristian.dumitrescu@intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--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).