From: Thomas Monjalon <thomas@monjalon.net>
To: "Ji, Kai" <kai.ji@intel.com>, Akhil Goyal <gakhil@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [EXTERNAL] [PATCH v7] examples: add Wycheproof validation app
Date: Fri, 25 Sep 2026 18:32:14 +0200 [thread overview]
Message-ID: <Uoji51ajRt-6kVG_ZXgD_Q@monjalon.net> (raw)
In-Reply-To: <CO6PR18MB4484077A45CBFCF6CB562E20D8812@CO6PR18MB4484.namprd18.prod.outlook.com>
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.
next prev parent reply other threads:[~2026-09-25 16:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 15:51 [PATCH] examples: add Wycheproof validation app Kai Ji
2026-09-15 16:58 ` Stephen Hemminger
2026-09-15 18:28 ` Stephen Hemminger
2026-09-17 15:34 ` [PATCH v3] " Kai Ji
2026-09-21 12:05 ` [EXTERNAL] " Gowrishankar Muthukrishnan
2026-09-21 16:41 ` Stephen Hemminger
2026-09-22 14:47 ` [PATCH v4] " Kai Ji
2026-09-22 16:05 ` [PATCH v5] " Kai Ji
2026-09-22 16:26 ` Stephen Hemminger
2026-09-23 10:50 ` [PATCH v6] " Kai Ji
2026-09-23 15:04 ` [PATCH v7] " Kai Ji
2026-09-24 14:35 ` [EXTERNAL] " Akhil Goyal
2026-09-24 15:01 ` Ji, Kai
2026-09-24 18:00 ` Akhil Goyal
2026-09-25 16:32 ` Thomas Monjalon [this message]
2026-09-29 16:12 ` Ji, Kai
2026-09-29 18:21 ` Akhil Goyal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Uoji51ajRt-6kVG_ZXgD_Q@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox