| /dpdk/doc/guides/prog_guide/ |
| H A D | traffic_metering_and_policing.rst | 21 * Policer actions (per meter output color): recolor, drop 23 * Chaining multiple meter objects 38 dedicated "meter" flow action. One or several "meter" actions can be registered 60 * There is a meter policy API to manage pre-defined policies for meter. 79 the traffic meter and policing library. 82 traffic meter and policing library. 85 #. The application creates the required meter profiles by using the 90 function. One of the previously created meter profile 91 (``struct rte_mtr_params::meter_profile_id``) and meter policy 97 meter object ID set to this meter object. [all …]
|
| /dpdk/app/test-pmd/ |
| H A D | cmdline_mtr.c | 199 cmdline_fixed_string_t meter; member 300 cmdline_fixed_string_t meter; member 321 meter, "meter"); 408 cmdline_fixed_string_t meter; member 430 meter, "meter"); 523 cmdline_fixed_string_t meter; member 546 meter, "meter"); 643 cmdline_fixed_string_t meter; member 659 meter, "meter"); 713 cmdline_fixed_string_t meter; member [all …]
|
| /dpdk/examples/pipeline/examples/ |
| H A D | meter.cli | 5 ; ./build/examples/dpdk-pipeline -l0-1 -- -s ./examples/pipeline/examples/meter.cli 26 pipeline PIPELINE0 build ./examples/pipeline/examples/meter.spec 28 pipeline PIPELINE0 meter profile platinum add cir 46000000 pir 138000000 cbs 1000000 pbs 1000000 29 pipeline PIPELINE0 meter meters from 0 to 15 set profile platinum
|
| H A D | meter.spec | 5 ; Every input packet (Ethernet/IPv4) is metered by the meter at the location indexed by the IPv4 10 ; meter in the array. 59 meter meters h.ipv4.src_addr h.ipv4.total_len 0 m.port_out
|
| /dpdk/lib/pipeline/ |
| H A D | rte_swx_pipeline_internal.h | 883 struct meter { struct 3511 struct meter *m; in __instr_metprefetch_h_exec() 3524 struct meter *m; in __instr_metprefetch_m_exec() 3537 struct meter *m; in __instr_metprefetch_i_exec() 3548 struct meter *m; in __instr_meter_hhm_exec() 3581 struct meter *m; in __instr_meter_hhi_exec() 3614 struct meter *m; in __instr_meter_hmm_exec() 3647 struct meter *m; in __instr_meter_hmi_exec() 3680 struct meter *m; in __instr_meter_mhm_exec() 3713 struct meter *m; in __instr_meter_mhi_exec() [all …]
|
| H A D | rte_swx_pipeline.c | 8913 meter_init(struct meter *m) in meter_init() 9962 struct meter *m; in rte_swx_ctl_meter_reset() 9991 struct meter *m; in rte_swx_ctl_meter_set() 10026 struct meter *m; in rte_swx_ctl_meter_stats_read() 10690 instr->meter.metarray_id); in instr_meter_export() 10700 instr->meter.idx.struct_id, in instr_meter_export() 10701 instr->meter.idx.n_bits, in instr_meter_export() 10702 instr->meter.idx.offset); in instr_meter_export() 10706 instr->meter.idx_val); in instr_meter_export() 10717 instr->meter.length.n_bits, in instr_meter_export() [all …]
|
| H A D | meson.build | 26 deps += ['port', 'table', 'meter', 'sched', 'cryptodev']
|
| /dpdk/doc/guides/sample_app_ug/ |
| 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. 72 The traffic meter parameters are configured in the application source code with following default v… 76 :start-after: Traffic meter parameters are configured in the application. 8< 77 :end-before: >8 End of traffic meter parameters are configured in the application.
|
| 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 …]
|
| /dpdk/doc/guides/tools/ |
| H A D | flow-perf.rst | 107 * ``--meter-profile-alg`` 109 Example: meter-profile-alg=srtcmp, default algorithm is srtcm_rfc2697 137 * ``--meter-profile=N1,N2,N3`` 141 Enable packet mode for meter profile. 394 Add policy-mtr to create meter with policy and specify policy actions. 397 * ``--meter`` 398 Add meter action to all flows actions. 399 Currently, 1 meter profile -> N meter rules -> N rte flows.
|
| /dpdk/lib/sched/ |
| H A D | meson.build | 18 deps += ['mbuf', 'meter']
|
| /dpdk/examples/qos_meter/ |
| H A D | meson.build | 10 deps += 'meter'
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_21_05.rst | 56 * **Updated meter API.** 58 * Added packet mode in the meter profile parameters data structures 61 * Added support for pre-defined meter policy via flow action list per color. 136 * Added support for pre-defined meter policy API. 137 * Added support for ASO (Advanced Steering Operation) meter. 249 * Added commands to create and delete meter policy: 250 ``add port meter policy (port_id) (policy_id) ...``. 254 * Added commands for action meter color to color the packet to reflect 255 the meter color result:
|
| /dpdk/lib/ethdev/ |
| H A D | meson.build | 40 deps += ['net', 'kvargs', 'meter', 'telemetry']
|
| /dpdk/doc/guides/testpmd_app_ug/ |
| H A D | testpmd_funcs.rst | 2793 delete port meter profile 2824 create port meter 2842 meter object. 2846 input color for the current meter object is determined by the latest meter 2852 enable port meter 2859 disable port meter 2866 delete port meter 2873 Set port meter profile 2880 set port meter dscp table 2899 show port meter stats [all …]
|
| /dpdk/doc/guides/nics/features/ |
| H A D | mvpp2.ini | 37 meter = Y key
|
| H A D | cnxk_vf.ini | 77 meter = Y key
|
| H A D | cnxk.ini | 85 meter = Y key
|
| H A D | default.ini | 157 meter = key
|
| H A D | mlx5.ini | 101 meter = Y key
|
| /dpdk/doc/guides/nics/ |
| H A D | mvpp2.rst | 588 - MTR object meter DSCP table update 601 2. Create meter profile: 605 testpmd> add port meter profile 0 0 srtcm_rfc2697 2000 256 256 607 3. Create meter: 611 testpmd> create port meter 0 0 0 yes d d d 0 1 0 613 4. Create flow rule witch meter attached: 617 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.
|
| H A D | mlx5.rst | 90 - Flow metering, including meter policy API. 91 - Flow meter hierarchy. 446 - The only supported meter policy actions: 452 - meter profile packet mode is supported. 1605 How to share a meter between ports in the same switch domain 1608 This section demonstrates how to use the shared meter. A meter M can be created 1615 How to use meter hierarchy 1619 A termination meter M can be the policy green action of another termination meter N. 1626 create port meter 0 M 1 1 yes 0xffff 1 0 1627 add port meter policy 0 2 g_actions meter mtr_id M / end y_actions end r_actions drop / end [all …]
|
| /dpdk/drivers/common/cnxk/ |
| H A D | meson.build | 79 includes += include_directories('../../../lib/meter')
|
| /dpdk/doc/api/ |
| H A D | doxy-api.conf.in | 60 @TOPDIR@/lib/meter \
|