On Thu, Jan 22, 2026 at 4:44 PM Andrew Bailey <[email protected]> wrote:
>
> Add cryptodev performance test suite. This test covers throughput
> performance metrics of various crypto devices using the
> dpdk-test-crypto-perf application. The results of this application will
> be compared against user supplied performance metrics and fail if signs
> of regression are apparent.
>
> Signed-off-by: Andrew Bailey <[email protected]>
<snip>
> +class Config(BaseConfig):
> + """Performance test metrics."""
> +
> + common_params: dict[str, int | float] = {
> + "Gbps Delta": 0.05,
> + }
> + throughput_test_parameters: list[dict[str, int | float | str]] = [
> + {
> + **common_params,
> + "buff_size": 64,
> + "mops": 9.85,
> + "gbps": 2.49,
> + },
> + {
> + **common_params,
> + "buff_size": 128,
> + "mops": 4.83,
> + "gbps": 4.95,
> + },
> + {
> + **common_params,
> + "buff_size": 256,
> + "mops": 4.77,
> + "gbps": 9.76,
> + },
> + {
> + **common_params,
> + "buff_size": 512,
> + "mops": 4.52,
> + "gbps": 18.52,
> + },
> + {
> + **common_params,
> + "buff_size": 1048,
> + "mops": 3.77,
> + "gbps": 30.87,
> + },
> + {
> + **common_params,
> + "buff_size": 2048,
> + "mops": 2.49,
> + "gbps": 40.86,
> + },
> + ]
Would it be worth creating a separate cryptodev config file in the
configurations directory, or adding a cryptodev section to the
tests_config.yaml file (similar to the single_core_forward_perf
suite)? I feel like this would be more consistent with the current
design of DTS, although if there's a good reason for the config class
being in the suite then disregard this.
Reviewed-by: Dean Marx <[email protected]>
