From: Radu Nicolau <radu.nicolau@intel.com>
To: Kai Ji <kai.ji@intel.com>
Cc: dev@dpdk.org, Radu Nicolau <radu.nicolau@intel.com>
Subject: [PATCH 4/5] app/crypto-perf: add support for SNOW-V
Date: Tue, 8 Apr 2025 12:19:49 +0100 [thread overview]
Message-ID: <20250408111952.2953492-4-radu.nicolau@intel.com> (raw)
In-Reply-To: <20250408111952.2953492-1-radu.nicolau@intel.com>
Add suport for SNOW-V and SNOW-V AEAD algorithms.
Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
---
app/test-crypto-perf/cperf_ops.c | 6 ++++--
doc/guides/tools/cryptoperf.rst | 2 ++
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/app/test-crypto-perf/cperf_ops.c b/app/test-crypto-perf/cperf_ops.c
index 37d06f1dea..f8c5bd6a4e 100644
--- a/app/test-crypto-perf/cperf_ops.c
+++ b/app/test-crypto-perf/cperf_ops.c
@@ -474,7 +474,8 @@ cperf_set_ops_cipher(struct rte_crypto_op **ops,
if (options->cipher_algo == RTE_CRYPTO_CIPHER_SNOW3G_UEA2 ||
options->cipher_algo == RTE_CRYPTO_CIPHER_KASUMI_F8 ||
- options->cipher_algo == RTE_CRYPTO_CIPHER_ZUC_EEA3)
+ options->cipher_algo == RTE_CRYPTO_CIPHER_ZUC_EEA3 ||
+ options->cipher_algo == RTE_CRYPTO_CIPHER_SNOW_V)
sym_op->cipher.data.length <<= 3;
sym_op->cipher.data.offset = 0;
@@ -633,7 +634,8 @@ cperf_set_ops_cipher_auth(struct rte_crypto_op **ops,
if (options->cipher_algo == RTE_CRYPTO_CIPHER_SNOW3G_UEA2 ||
options->cipher_algo == RTE_CRYPTO_CIPHER_KASUMI_F8 ||
- options->cipher_algo == RTE_CRYPTO_CIPHER_ZUC_EEA3)
+ options->cipher_algo == RTE_CRYPTO_CIPHER_ZUC_EEA3 ||
+ options->cipher_algo == RTE_CRYPTO_CIPHER_SNOW_V)
sym_op->cipher.data.length <<= 3;
sym_op->cipher.data.offset = 0;
diff --git a/doc/guides/tools/cryptoperf.rst b/doc/guides/tools/cryptoperf.rst
index 017e8ef934..72774e04cd 100644
--- a/doc/guides/tools/cryptoperf.rst
+++ b/doc/guides/tools/cryptoperf.rst
@@ -223,6 +223,7 @@ The following are the application command-line options:
kasumi-f8
snow3g-uea2
zuc-eea3
+ snow-v
* ``--cipher-op <mode>``
@@ -287,6 +288,7 @@ The following are the application command-line options:
aes-ccm
aes-gcm
+ snow-v-aead
* ``--aead-op <mode>``
--
2.43.0
next prev parent reply other threads:[~2025-04-08 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 11:19 [PATCH 1/5] crypto/ipsec_mb: " Radu Nicolau
2025-04-08 11:19 ` [PATCH 2/5] examples/l2fwd-crypto: " Radu Nicolau
2025-04-08 11:19 ` [PATCH 3/5] tests: add unit tests and test vectors " Radu Nicolau
2025-04-08 11:19 ` Radu Nicolau [this message]
2025-04-08 11:19 ` [PATCH 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=20250408111952.2953492-4-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).