DPDK patches and discussions
 help / color / mirror / Atom feed
From: Eelco Chaudron <echaudro@redhat.com>
To: cristian.dumitrescu@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v4 0/2] lib/librte_meter: add RFC4115 trTCM meter support
Date: Fri,  4 Jan 2019 13:59:33 +0000	[thread overview]
Message-ID: <154661036216.75321.4852909033090962683.stgit@dbuild> (raw)

This patch adds support for RFC4115 trTCM meters.


Signed-off-by: Eelco Chaudron <echaudro@redhat.com>

v4:
 - Fixed typo
 - Cleaned up code to be aligned with RFC diagram

v3:
 - Gave the rfc4115 meter it's own data structures

v2:
 - Marked all functions with __rte_experimental, and added
   "EXPERIMENTAL:..." to doxygen comments.
 - Removed library version change, and merged it with first patch
 - Do not call rte_meter_trtcm_rfc4115_color_aware_check in
   rte_meter_trtcm_rfc4115_color_blind_check to avoid error with
   it being marked as experimental

Eelco Chaudron (2):
      lib/librte_meter: add RFC4115 trTCM meter support
      test/test_meter: update meter test to include RFC4115 meters


 lib/librte_meter/rte_meter.c           |   42 ++++++
 lib/librte_meter/rte_meter.h           |  233 ++++++++++++++++++++++++++++++++
 lib/librte_meter/rte_meter_version.map |    9 +
 test/test/test_meter.c                 |  212 +++++++++++++++++++++++++++++
 4 files changed, 494 insertions(+), 2 deletions(-)

             reply	other threads:[~2019-01-04 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 13:59 Eelco Chaudron [this message]
2019-01-04 13:59 ` [dpdk-dev] [PATCH v4 1/2] " Eelco Chaudron
2019-01-04 19:42   ` Stephen Hemminger
2019-01-07  7:41     ` Eelco Chaudron
2019-01-07 15:54       ` Dumitrescu, Cristian
2019-01-04 13:59 ` [dpdk-dev] [PATCH v4 2/2] test/test_meter: update meter test to include RFC4115 meters Eelco Chaudron
2019-01-07 15:58 ` [dpdk-dev] [PATCH v4 0/2] lib/librte_meter: add RFC4115 trTCM meter support Dumitrescu, Cristian
2019-01-09 23:22   ` Thomas Monjalon
2019-01-10  8:25     ` Eelco Chaudron

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=154661036216.75321.4852909033090962683.stgit@dbuild \
    --to=echaudro@redhat.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    /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).