summaryrefslogtreecommitdiff
path: root/examples/ip_pipeline/Makefile
diff options
context:
space:
mode:
authorCristian Dumitrescu <cristian.dumitrescu@intel.com>2018-01-08 15:43:56 +0000
committerThomas Monjalon <thomas@monjalon.net>2018-02-19 22:28:05 +0100
commitc06ddf9698e0c2a9653cfa971f9ddc205065662c (patch)
tree85a5166a43d5952a058643c9cca22403926491ef /examples/ip_pipeline/Makefile
parent3d8d90206c4dbe925aff8c5c7950cdfd2484b66f (diff)
downloaddpdk-c06ddf9698e0c2a9653cfa971f9ddc205065662c.zip
dpdk-c06ddf9698e0c2a9653cfa971f9ddc205065662c.tar.gz
dpdk-c06ddf9698e0c2a9653cfa971f9ddc205065662c.tar.xz
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>
Diffstat (limited to 'examples/ip_pipeline/Makefile')
-rw-r--r--examples/ip_pipeline/Makefile2
1 files changed, 2 insertions, 0 deletions
diff --git a/examples/ip_pipeline/Makefile b/examples/ip_pipeline/Makefile
index 27f7cc6..85fbbaf 100644
--- a/examples/ip_pipeline/Makefile
+++ b/examples/ip_pipeline/Makefile
@@ -48,6 +48,7 @@ LDFLAGS_STATIC = -Wl,-Bstatic $(shell pkg-config --static --libs libdpdk)
VPATH += pipeline
CFLAGS += -I. -I./pipeline/
+CFLAGS += -DALLOW_EXPERIMENTAL_API
OBJS := $(patsubst %.c,build/%.o,$(SRCS-y))
@@ -88,6 +89,7 @@ SRCS-$(CONFIG_RTE_LIBRTE_PIPELINE) := $(SRCS-y)
CFLAGS += -I$(SRCDIR) -I$(SRCDIR)/pipeline
CFLAGS += -O3
CFLAGS += $(WERROR_FLAGS) -Wno-error=unused-function -Wno-error=unused-variable
+CFLAGS += -DALLOW_EXPERIMENTAL_API
include $(RTE_SDK)/mk/rte.extapp.mk