DPDK patches and discussions
 help / color / mirror / Atom feed
From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-tm 17.11 pre-rc2
Date: Fri, 20 Oct 2017 15:39:45 +0100	[thread overview]
Message-ID: <1508510385-238968-1-git-send-email-cristian.dumitrescu@intel.com> (raw)

The following changes since commit 6b9ed026a8704b9e5ee5da7997617ef7cc82e114:

  igb_uio: fix build with kernel <= 3.17 (2017-10-16 13:07:11 +0200)

are available in the git repository at:

  http://dpdk.org/git/next/dpdk-next-tm 

for you to fetch changes up to d5b0bd08a6064565515fd9e52ed2060693d224eb:

  app/test-pmd: add CLI for TM nodes and hierarchy commit (2017-10-20 15:02:33 +0100)

----------------------------------------------------------------
Cristian Dumitrescu (5):
      ethdev: add new flow action for metering and policing
      ethdev: add new eth_dev_ops function for mtr ops get
      ethdev: add new api for traffic metering and policing
      doc: ethdev traffic metering and policing api
      app/testpmd: cli for traffic metering and policing

Jasvinder Singh (3):
      app/test-pmd: add CLI for TM capability and stats
      app/test-pmd: add CLI for shaper and wred profiles
      app/test-pmd: add CLI for TM nodes and hierarchy commit

 MAINTAINERS                                        |    4 +
 app/test-pmd/Makefile                              |    2 +
 app/test-pmd/cmdline.c                             |  121 ++
 app/test-pmd/cmdline_flow.c                        |   24 +
 app/test-pmd/cmdline_mtr.c                         | 1020 ++++++++++
 app/test-pmd/cmdline_mtr.h                         |   49 +
 app/test-pmd/cmdline_tm.c                          | 2067 ++++++++++++++++++++
 app/test-pmd/cmdline_tm.h                          |   56 +
 doc/api/doxy-api-index.md                          |    1 +
 doc/guides/prog_guide/index.rst                    |    1 +
 doc/guides/prog_guide/rte_flow.rst                 |   23 +
 .../prog_guide/traffic_metering_and_policing.rst   |  102 +
 lib/librte_ether/Makefile                          |    3 +
 lib/librte_ether/rte_ethdev.h                      |    7 +
 lib/librte_ether/rte_ethdev_version.map            |   18 +
 lib/librte_ether/rte_flow.h                        |   22 +
 lib/librte_ether/rte_mtr.c                         |  229 +++
 lib/librte_ether/rte_mtr.h                         |  730 +++++++
 lib/librte_ether/rte_mtr_driver.h                  |  221 +++
 19 files changed, 4700 insertions(+)
 create mode 100644 app/test-pmd/cmdline_mtr.c
 create mode 100644 app/test-pmd/cmdline_mtr.h
 create mode 100644 app/test-pmd/cmdline_tm.c
 create mode 100644 app/test-pmd/cmdline_tm.h
 create mode 100644 doc/guides/prog_guide/traffic_metering_and_policing.rst
 create mode 100644 lib/librte_ether/rte_mtr.c
 create mode 100644 lib/librte_ether/rte_mtr.h
 create mode 100644 lib/librte_ether/rte_mtr_driver.h

             reply	other threads:[~2017-10-20 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-20 14:39 Cristian Dumitrescu [this message]
2017-10-23 13:17 ` 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=1508510385-238968-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).