Hi dean, Thank you for the review. The current implementation does draw values from tests_config.yaml file, and the config class is how those values are drawn from the config into the test suite. I realize this may be confusing as I had failed to update the tests_config.example in this version. This will be updated with my v2, thank you for pointing this out.
> 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]> >
