From: Marko Kovacevic <marko.kovacevic@intel.com>
To: dev@dpdk.org
Cc: akhil.goyal@nxp.com, roy.fan.zhang@intel.com,
Marko Kovacevic <marko.kovacevic@intel.com>
Subject: [dpdk-dev] [PATCH v1 0/2] FIPS validation capability
Date: Fri, 7 Sep 2018 18:13:09 +0100 [thread overview]
Message-ID: <20180907171311.20371-1-marko.kovacevic@intel.com> (raw)
Adding capability into DPDK to allow certification for FIPS
validation, I have just added one test for one algo will be adding other
algos into other versions of the patch and i will be refactoring the code and
cleaning the parser once i start adding the different algos.
Marko Kovacevic (2):
test/test: cryptodev application for FIPS certification
test/test: cryptodev application parser for FIPS certification
test/test/Makefile | 4 +
test/test/test_cryptodev_fips.c | 771 +++++++++++++++++++++++++++
test/test/test_cryptodev_fips_parse.h | 156 ++++++
test/test/test_cryptodev_fips_parse_aes.c | 399 ++++++++++++++
test/test/test_cryptodev_fips_parse_common.c | 330 ++++++++++++
5 files changed, 1660 insertions(+)
create mode 100644 test/test/test_cryptodev_fips.c
create mode 100644 test/test/test_cryptodev_fips_parse.h
create mode 100644 test/test/test_cryptodev_fips_parse_aes.c
create mode 100644 test/test/test_cryptodev_fips_parse_common.c
--
2.9.5
next reply other threads:[~2018-09-07 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 17:13 Marko Kovacevic [this message]
2018-09-07 17:13 ` [dpdk-dev] [PATCH v1 1/2] test/test: cryptodev application for FIPS certification Marko Kovacevic
2018-09-07 17:13 ` [dpdk-dev] [PATCH v1 2/2] test/test: cryptodev application parser " Marko Kovacevic
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=20180907171311.20371-1-marko.kovacevic@intel.com \
--to=marko.kovacevic@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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;
as well as URLs for NNTP newsgroup(s).