numam-dpdk/doc/guides
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
..
bbdevs bb/turbo_sw: add software turbo driver 2018-01-19 01:44:25 +01:00
contributing doc: add maintainers section to the contributors guide 2018-02-14 00:23:25 +01:00
cryptodevs doc: fix outdated link to IPsec white paper 2018-02-14 18:43:12 +01:00
eventdevs doc: convert Intel license headers to SPDX tags 2018-02-06 23:27:08 +01:00
faq doc: convert Intel license headers to SPDX tags 2018-02-06 23:27:08 +01:00
freebsd_gsg doc: convert Intel license headers to SPDX tags 2018-02-06 23:27:08 +01:00
howto doc: convert Intel license headers to SPDX tags 2018-02-06 23:27:08 +01:00
linux_gsg doc: remove reference to old distro in Linux guide 2018-02-14 18:35:18 +01:00
mempool doc: remove unused config options 2018-01-16 18:47:49 +01:00
nics doc: add note for shared library in NICs guide 2018-02-13 23:59:00 +01:00
platform doc: use SPDX tag for Cavium copyright files 2018-01-09 16:19:01 +01:00
prog_guide doc: convert Intel license headers to SPDX tags 2018-02-06 23:27:08 +01:00
rel_notes meter: add configuration profile 2018-02-19 22:28:05 +01:00
sample_app_ug doc: update callback functions in pipeline sample guide 2018-02-08 22:54:09 +01:00
testpmd_app_ug doc: convert Intel license headers to SPDX tags 2018-02-06 23:27:08 +01:00
tools doc: update limitations in procinfo guide 2018-02-08 23:06:37 +01:00
conf.py doc: improve HTML spacing in release notes 2018-02-14 00:23:25 +01:00
custom.css doc: improve HTML spacing in release notes 2018-02-14 00:23:25 +01:00
index.rst doc: convert Intel license headers to SPDX tags 2018-02-06 23:27:08 +01:00