24/09/2026 20:00, Akhil Goyal: > > Wycheproof differs somewhat from the existing cryptodev test vectors in > > that it is > > an externally maintained collection of JSON test suites covering a large > > number of > > edge cases and negative tests. The intended usage model is to load the > > upstream > > vector files at runtime rather than embedding them in the DPDK tree. > > I think the existing examples/fips_validation application follows a similar > > approach, consuming external CAVP/ACVP vector files rather than integrating > > them into dpdk-test. This patch follows that precedent, with the goal of > > providing > > file-driven conformance validation as a standalone example application. > > I agree that the documentation can be improved. At minimum, the .rst should > > describe where the Wycheproof vectors can be obtained and reference the > > applicable upstream license, as the current example command may give the > > impression that the vector files are included in the DPDK source tree when > > they > > are not. > > Ok, so in that case did you consider integrating this app into > fips_validation app.. > May be we could rename fips_validation to crypto_validation and internally > have 2 modes - > Fips and Wycheproof? Like what we have for examples/multi_process?
I like this proposal.
