c06ddf9698
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>
73 lines
1.8 KiB
C
73 lines
1.8 KiB
C
/* SPDX-License-Identifier: BSD-3-Clause
|
|
* Copyright(c) 2010-2014 Intel Corporation
|
|
*/
|
|
|
|
#ifndef _MAIN_H_
|
|
#define _MAIN_H_
|
|
|
|
enum policer_action {
|
|
GREEN = e_RTE_METER_GREEN,
|
|
YELLOW = e_RTE_METER_YELLOW,
|
|
RED = e_RTE_METER_RED,
|
|
DROP = 3,
|
|
};
|
|
|
|
enum policer_action policer_table[e_RTE_METER_COLORS][e_RTE_METER_COLORS] =
|
|
{
|
|
{ GREEN, RED, RED},
|
|
{ DROP, YELLOW, RED},
|
|
{ DROP, DROP, RED}
|
|
};
|
|
|
|
#if APP_MODE == APP_MODE_FWD
|
|
|
|
#define FUNC_METER(m, p, time, pkt_len, pkt_color) \
|
|
({ \
|
|
void *mp = m; \
|
|
void *pp = p; \
|
|
mp = mp; \
|
|
pp = pp; \
|
|
time = time; \
|
|
pkt_len = pkt_len; \
|
|
pkt_color; \
|
|
})
|
|
#define FUNC_CONFIG(a, b) 0
|
|
#define FLOW_METER int
|
|
#define PROFILE app_srtcm_profile
|
|
|
|
#elif APP_MODE == APP_MODE_SRTCM_COLOR_BLIND
|
|
|
|
#define FUNC_METER(m, p, time, pkt_len, pkt_color) \
|
|
rte_meter_srtcm_color_blind_check(m, p, time, pkt_len)
|
|
#define FUNC_CONFIG rte_meter_srtcm_config
|
|
#define FLOW_METER struct rte_meter_srtcm
|
|
#define PROFILE app_srtcm_profile
|
|
|
|
#elif (APP_MODE == APP_MODE_SRTCM_COLOR_AWARE)
|
|
|
|
#define FUNC_METER rte_meter_srtcm_color_aware_check
|
|
#define FUNC_CONFIG rte_meter_srtcm_config
|
|
#define FLOW_METER struct rte_meter_srtcm
|
|
#define PROFILE app_srtcm_profile
|
|
|
|
#elif (APP_MODE == APP_MODE_TRTCM_COLOR_BLIND)
|
|
|
|
#define FUNC_METER(m, p, time, pkt_len, pkt_color) \
|
|
rte_meter_trtcm_color_blind_check(m, p, time, pkt_len)
|
|
#define FUNC_CONFIG rte_meter_trtcm_config
|
|
#define FLOW_METER struct rte_meter_trtcm
|
|
#define PROFILE app_trtcm_profile
|
|
|
|
#elif (APP_MODE == APP_MODE_TRTCM_COLOR_AWARE)
|
|
|
|
#define FUNC_METER rte_meter_trtcm_color_aware_check
|
|
#define FUNC_CONFIG rte_meter_trtcm_config
|
|
#define FLOW_METER struct rte_meter_trtcm
|
|
#define PROFILE app_trtcm_profile
|
|
|
|
#else
|
|
#error Invalid value for APP_MODE
|
|
#endif
|
|
|
|
#endif /* _MAIN_H_ */
|