From: Radu Nicolau <radu.nicolau@intel.com>
Cc: dev@dpdk.org, kai.ji@intel.com, Radu Nicolau <radu.nicolau@intel.com>
Subject: [PATCH v2 0/5] add SNOW-V support in ipsec_mb PMD
Date: Fri, 11 Apr 2025 11:09:36 +0100 [thread overview]
Message-ID: <20250411101425.3041736-1-radu.nicolau@intel.com> (raw)
Add support for SNOW-V and SNOW-V AEAD in ipsec_mb PMD.
Add unit tests and test vectors for SNOW-V and SNOW-V AEAD.
Add support in cryptoperf and eventdev test apps.
Radu Nicolau (5):
crypto/ipsec_mb: add support for SNOW-V
examples/l2fwd-crypto: add support for SNOW-V
tests: add unit tests and test vectors for SNOW-V
app/crypto-perf: add support for SNOW-V
app/eventdev: update eventdev app for SNOW-V
app/test-crypto-perf/cperf_ops.c | 6 +-
app/test-eventdev/evt_options.c | 3 +-
app/test/test_cryptodev.c | 599 ++++++++++++++++++
app/test/test_cryptodev_aead_test_vectors.h | 275 ++++++++
app/test/test_cryptodev_snow_v_test_vectors.h | 213 +++++++
doc/guides/cryptodevs/aesni_mb.rst | 2 +
doc/guides/tools/cryptoperf.rst | 2 +
drivers/crypto/ipsec_mb/pmd_aesni_mb.c | 70 +-
drivers/crypto/ipsec_mb/pmd_aesni_mb_priv.h | 52 ++
examples/l2fwd-crypto/main.c | 3 +-
10 files changed, 1217 insertions(+), 8 deletions(-)
create mode 100644 app/test/test_cryptodev_snow_v_test_vectors.h
--
2.43.0
next reply other threads:[~2025-04-11 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 10:09 Radu Nicolau [this message]
2025-04-11 10:09 ` [PATCH v2 1/5] crypto/ipsec_mb: add support for SNOW-V Radu Nicolau
2025-04-11 10:09 ` [PATCH v2 2/5] examples/l2fwd-crypto: " Radu Nicolau
2025-04-11 10:09 ` [PATCH v2 3/5] tests: add unit tests and test vectors " Radu Nicolau
2025-04-11 10:09 ` [PATCH v2 4/5] app/crypto-perf: add support " Radu Nicolau
2025-04-11 10:09 ` [PATCH v2 5/5] app/eventdev: update eventdev app " Radu Nicolau
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=20250411101425.3041736-1-radu.nicolau@intel.com \
--to=radu.nicolau@intel.com \
--cc=dev@dpdk.org \
--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;
as well as URLs for NNTP newsgroup(s).