| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | traffic_metering_and_policing.rst | 21 * Policer actions (per meter output color): recolor, drop 28 which is why the MTR objects are enabled through a special "meter" action. 37 dedicated "meter" flow action. One or several "meter" actions can be registered 51 * Traffic metering: The packet is assigned a color (the meter output color) 59 * Policing: There is a separate policer action configured for each meter 64 * Keep the same packet color: the policer output color matches the meter 68 than the meter output color. The policer output color is the output color
|
| H A D | qos_framework.rst | 1678 These algorithms meter the stream of incoming packets based on the allowance defined in advance for…
|
| H A D | rte_flow.rst | 1925 the meter action. The MTR object can be further updated or queried using
|
| /f-stack/dpdk/app/test-pmd/ |
| H A D | cmdline_mtr.c | 237 cmdline_fixed_string_t meter; member 330 cmdline_fixed_string_t meter; member 350 meter, "meter"); 431 cmdline_fixed_string_t meter; member 452 meter, "meter"); 539 cmdline_fixed_string_t meter; member 561 meter, "meter"); 651 cmdline_fixed_string_t meter; member 667 meter, "meter"); 721 cmdline_fixed_string_t meter; member [all …]
|
| H A D | meson.build | 27 deps += ['ethdev', 'gro', 'gso', 'cmdline', 'metrics', 'meter', 'bus_pci']
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | ip_pipeline.rst | 336 [meter srtcm | trtcm 468 [meter 469 tc0 meter <meter_profile_id> policer g <pa> y <pa> r <pa> 470 [tc1 meter <meter_profile_id> policer g <pa> y <pa> r <pa> 471 tc2 meter <meter_profile_id> policer g <pa> y <pa> r <pa> 472 tc3 meter <meter_profile_id> policer g <pa> y <pa> r <pa>]] 524 Add meter profile to the table for specific pipeline instance :: 526 pipeline <pipeline_name> table <table_id> meter profile <meter_profile_id> 530 Delete meter profile from the table for specific pipeline instance :: 533 meter profile <meter_profile_id> delete [all …]
|
| H A D | qos_metering.rst | 7 The QoS meter sample application is an example that demonstrates the use of DPDK to provide QoS mar… 17 …anner depending on both the input and output colors of the packets that are processed by the meter. 77 The traffic meter parameters are configured in the application source code with following default v…
|
| /f-stack/dpdk/lib/librte_sched/ |
| H A D | meson.build | 7 deps += ['mbuf', 'meter']
|
| /f-stack/dpdk/lib/librte_pipeline/ |
| H A D | meson.build | 16 deps += ['port', 'table', 'meter', 'sched', 'cryptodev']
|
| /f-stack/dpdk/examples/qos_meter/ |
| H A D | meson.build | 10 deps += 'meter'
|
| /f-stack/dpdk/lib/librte_ethdev/ |
| H A D | meson.build | 29 deps += ['net', 'kvargs', 'meter', 'telemetry']
|
| /f-stack/dpdk/doc/guides/testpmd_app_ug/ |
| H A D | testpmd_funcs.rst | 2737 delete port meter profile 2744 create port meter 2764 meter object. 2768 input color for the current meter object is determined by the latest meter 2774 enable port meter 2781 disable port meter 2788 delete port meter 2795 Set port meter profile 2802 set port meter dscp table 2828 set port meter stats mask [all …]
|
| /f-stack/dpdk/lib/ |
| H A D | meson.build | 17 'mempool', 'mbuf', 'net', 'meter', 'ethdev', 'pci', # core 45 'mempool', 'mbuf', 'net', 'meter', 'ethdev', 'pci',
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | mvpp2.rst | 543 - MTR object meter DSCP table update 556 2. Create meter profile: 560 testpmd> add port meter profile 0 0 srtcm_rfc2697 2000 256 256 562 3. Create meter: 566 testpmd> create port meter 0 0 0 yes d d d 0 1 0 568 4. Create flow rule witch meter attached: 572 testpmd> flow create 0 ingress pattern ipv4 src is 10.10.10.1 / end actions meter mtr_id 0 / end
|
| H A D | softnic.rst | 283 algorithm. For the meter output color, policer actions like 289 The SoftNIC does not support the meter object shared by several flows, 290 thus only supports creating meter object private to the flow. Once meter 292 specifying the ``meter`` flow action in the flow rule.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/arm/ |
| H A D | vexpress-sysreg.txt | 86 - some functions (eg. energy meter, with its 64 bit long counter)
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_18_05.rst | 397 * meter: API updated to accommodate configuration profiles. 399 The meter API has been changed to support meter configuration profiles. The 401 for a given meter object, such as the rates and sizes for the token 402 buckets. These configuration parameters were previously part of the meter 404 parameters from the meter object data structure results in reducing its 406 of meter objects are used.
|
| H A D | release_19_05.rst | 277 * meter: replace ``enum rte_meter_color`` in the meter library with new
|
| /f-stack/dpdk/drivers/net/mvpp2/ |
| H A D | mrvl_flow.c | 2259 const struct rte_flow_action_meter *meter; in mrvl_flow_parse_actions() local 2262 meter = action->conf; in mrvl_flow_parse_actions() 2263 if (!meter) in mrvl_flow_parse_actions() 2269 if (mtr->mtr_id == meter->mtr_id) in mrvl_flow_parse_actions()
|
| /f-stack/dpdk/drivers/net/mlx5/ |
| H A D | mlx5_flow.h | 1037 uint32_t meter:16; /**< Holds flow meter id. */ member
|
| H A D | mlx5_flow_dv.c | 10147 if (!flow->meter) { in flow_dv_translate() 10157 flow->meter = fm->idx; in flow_dv_translate() 10162 [MLX5_IPOOL_MTR], flow->meter); in flow_dv_translate() 11248 if (flow->meter) { in flow_dv_destroy() 11252 flow->meter); in flow_dv_destroy() 11255 flow->meter = 0; in flow_dv_destroy()
|