| acca5cf4 | 11-Nov-2021 |
Rongwei Liu <[email protected]> |
app/flow-perf: support dynamic values for meter profile
Change meter-cir option to meter-profile to cover user input for CIR, CBS & EBS values.
The usage is as below: --meter-profile=N1,N2,N3 defau
app/flow-perf: support dynamic values for meter profile
Change meter-cir option to meter-profile to cover user input for CIR, CBS & EBS values.
The usage is as below: --meter-profile=N1,N2,N3 default value is 1250000 156250 0.
Signed-off-by: Rongwei Liu <[email protected]> Acked-by: Wisam Jaddo <[email protected]>
show more ...
|
| 7f37f093 | 11-Nov-2021 |
Rongwei Liu <[email protected]> |
app/flow-perf: support meter policy API
Add option "policy-mtr" to indicate if meter creation will include policy or not. Meter creation will keep unchanged without it.
With "policy-mtr", the polic
app/flow-perf: support meter policy API
Add option "policy-mtr" to indicate if meter creation will include policy or not. Meter creation will keep unchanged without it.
With "policy-mtr", the policy is introduced. API create_meter_policy is to create a policy. API create_meter_rule will use it to create a meter. The value of it is used to specify meter policy actions.
Signed-off-by: Haifei Luo <[email protected]> Signed-off-by: Jiawei Wang <[email protected]> Signed-off-by: Rongwei Liu <[email protected]> Acked-by: Wisam Jaddo <[email protected]>
show more ...
|
| 83f9be10 | 14-Mar-2021 |
Wisam Jaddo <[email protected]> |
app/flow-perf: fix encap/decap actions
When using decap actions it's been set to the data to decap into the encap_data instead of decap_data, as a results we end up with bad encap and decap data in
app/flow-perf: fix encap/decap actions
When using decap actions it's been set to the data to decap into the encap_data instead of decap_data, as a results we end up with bad encap and decap data in many cases.
Fixes: 0c8f1f4ab90e ("app/flow-perf: support raw encap/decap actions") Cc: [email protected]
Signed-off-by: Wisam Jaddo <[email protected]> Acked-by: Alexander Kozyrev <[email protected]>
show more ...
|
| 96923deb | 14-Mar-2021 |
Wisam Jaddo <[email protected]> |
app/flow-perf: report first flow latency
Starting from this commit the app will always report the first flow latency.
This is useful in debugging to check the first flow insertion before any cachin
app/flow-perf: report first flow latency
Starting from this commit the app will always report the first flow latency.
This is useful in debugging to check the first flow insertion before any caching effect.
Signed-off-by: Wisam Jaddo <[email protected]> Acked-by: Alexander Kozyrev <[email protected]>
show more ...
|
| f2cb9393 | 14-Mar-2021 |
Wisam Jaddo <[email protected]> |
app/flow-perf: fix IPv6 source address increment
Currently the memset() will not set a correct src ip that represent the incremental value of the counter.
This commit will fix this and each flow wi
app/flow-perf: fix IPv6 source address increment
Currently the memset() will not set a correct src ip that represent the incremental value of the counter.
This commit will fix this and each flow will have correct IPv6.src that it's incremental from previous flow and equal to the decimal values.
Fixes: bf3688f1e816 ("app/flow-perf: add insertion rate calculation") Cc: [email protected]
Signed-off-by: Wisam Jaddo <[email protected]> Acked-by: Alexander Kozyrev <[email protected]>
show more ...
|
| b22a5a1e | 14-Mar-2021 |
Wisam Jaddo <[email protected]> |
app/flow-perf: skip dumps for masked ports
Take into consideration that the user may call portmask for any run, thus the app should always check if port is needed to collect and report or not.
Fixe
app/flow-perf: skip dumps for masked ports
Take into consideration that the user may call portmask for any run, thus the app should always check if port is needed to collect and report or not.
Fixes: 070316d01d3e ("app/flow-perf: add multi-core rule insertion and deletion") Fixes: d8099d7ecbd0 ("app/flow-perf: split dump functions") Cc: [email protected]
Signed-off-by: Wisam Jaddo <[email protected]> Acked-by: Alexander Kozyrev <[email protected]>
show more ...
|
| c304358e | 14-Mar-2021 |
Wisam Jaddo <[email protected]> |
app/flow-perf: rename records of used CPU time
create_flow and create_meter are not correct names since those are records that contain creation and deletion, which makes them more of a record for su
app/flow-perf: rename records of used CPU time
create_flow and create_meter are not correct names since those are records that contain creation and deletion, which makes them more of a record for such data.
Fixes: d8099d7ecbd0 ("app/flow-perf: split dump functions") Cc: [email protected]
Signed-off-by: Wisam Jaddo <[email protected]> Acked-by: Alexander Kozyrev <[email protected]>
show more ...
|
| eb4df25f | 14-Mar-2021 |
Wisam Jaddo <[email protected]> |
app/flow-perf: add runtime option to use unique data
Current support for unique data is to compile with config.h var FIXED_VALUES as 0, and this is only supported on compilation time, as a result th
app/flow-perf: add runtime option to use unique data
Current support for unique data is to compile with config.h var FIXED_VALUES as 0, and this is only supported on compilation time, as a result the user may use only single mode for each compilation.
Starting with this commit the user will have the ability to use this feature on the fly by using this new option: --unique-data
Example of unique data usage: Insert many rules with different encap data for a flows that have encap action in it.
Signed-off-by: Wisam Jaddo <[email protected]> Acked-by: Alexander Kozyrev <[email protected]>
show more ...
|
| 6a2cf58a | 19-Jan-2021 |
Dong Zhou <[email protected]> |
app/flow-perf: support meter action
Currently, test-flow-perf app cannot generate flows with meter action. This patch introduces new parameter "--meter" to generate flows with meter action.
Signed-
app/flow-perf: support meter action
Currently, test-flow-perf app cannot generate flows with meter action. This patch introduces new parameter "--meter" to generate flows with meter action.
Signed-off-by: Dong Zhou <[email protected]> Reviewed-by: Wisam Jaddo <[email protected]> Reviewed-by: Alexander Kozyrev <[email protected]>
show more ...
|