Go to file
Cristian Dumitrescu c06ddf9698 meter: add configuration profile
This patch adds support for meter configuration profiles.
Benefits: simplified configuration procedure, improved performance.

Q1: What is the configuration profile and why does it make sense?
A1: The configuration profile represents the set of configuration
    parameters for a given meter object, such as the rates and sizes for
    the token buckets. The configuration profile concept makes sense when
    many meter objects share the same configuration, which is the typical
    usage model: thousands of traffic flows are each individually metered
    according to just a few service levels (i.e. profiles).

Q2: How is the configuration profile improving the performance?
A2: The performance improvement is achieved by reducing the memory
    footprint of a meter object, which results in better cache utilization
    for the typical case when large arrays of meter objects are used. The
    internal data structures stored for each meter object contain:
       a) Constant fields: Low level translation of the configuration
          parameters that does not change post-configuration. This is
          really duplicated for all meters that use the same
          configuration. This is the configuration profile data that is
          moved away from the meter object. Current size (implementation
          dependent): srTCM = 32 bytes, trTCM = 32 bytes.
       b) Variable fields: Time stamps and running counters that change
          during the on-going traffic metering process. Current size
          (implementation dependent): srTCM = 24 bytes, trTCM = 32 bytes.
          Therefore, by moving the constant fields to a separate profile
          data structure shared by all the meters with the same
          configuration, the size of the meter object is reduced by ~50%.

Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
2018-02-19 22:28:05 +01:00
app app/testpmd: fix flow director filter 2018-02-08 22:27:50 +01:00
buildtools buildtools: output build failure reason to stderr 2018-02-08 22:25:37 +01:00
config build: add more implementers IDs and PNs for ARM 2018-02-06 14:44:31 +01:00
devtools compat: relicense some files 2018-02-06 23:13:47 +01:00
doc meter: add configuration profile 2018-02-19 22:28:05 +01:00
drivers net/failsafe: fix Rx interrupt reinstallation 2018-02-14 16:32:00 +01:00
examples meter: add configuration profile 2018-02-19 22:28:05 +01:00
lib meter: add configuration profile 2018-02-19 22:28:05 +01:00
license license: introduce SPDX identifiers 2018-01-04 22:41:38 +01:00
mk doc: improve HTML spacing in release notes 2018-02-14 00:23:25 +01:00
pkg version: 18.02.0 2018-02-14 19:11:02 +01:00
test meter: add configuration profile 2018-02-19 22:28:05 +01:00
usertools usertools/devbind: fix kernel module reporting 2018-02-06 02:18:45 +01:00
.gitattributes improve git diff 2016-11-13 15:25:12 +01:00
.gitignore devtools: add tags and cscope index generation 2017-04-30 12:57:04 +02:00
GNUmakefile license: use SPDX tag in root makefile 2018-01-04 22:41:38 +01:00
MAINTAINERS maintainers: update for stable branches 2018-02-14 00:42:04 +01:00
Makefile license: use SPDX tag in root makefile 2018-01-04 22:41:38 +01:00
meson_options.txt test: build app with meson as dpdk-test 2018-01-30 21:58:59 +01:00
meson.build build: detect micro-arch on ARM 2018-01-30 21:59:00 +01:00
README license: introduce SPDX identifiers 2018-01-04 22:41:38 +01:00

DPDK is a set of libraries and drivers for fast packet processing.
It supports many processor architectures and both FreeBSD and Linux.

The DPDK uses the Open Source BSD-3-Clause license for the core libraries
and drivers. The kernel components are GPL-2.0 licensed.

Please check the doc directory for release notes,
API documentation, and sample application information.

For questions and usage discussions, subscribe to: users@dpdk.org
Report bugs and issues to the development mailing list: dev@dpdk.org