DPDK patches and discussions
 help / color / mirror / Atom feed
From: Radu Nicolau <radu.nicolau@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, Fan Zhang <fanzhang.oss@gmail.com>
Cc: dev@dpdk.org, kai.ji@intel.com, Radu Nicolau <radu.nicolau@intel.com>
Subject: [PATCH v2 2/5] examples/l2fwd-crypto: add support for SNOW-V
Date: Fri, 11 Apr 2025 11:09:38 +0100	[thread overview]
Message-ID: <20250411101425.3041736-3-radu.nicolau@intel.com> (raw)
In-Reply-To: <20250411101425.3041736-1-radu.nicolau@intel.com>

Update l2fwd-crypto to be able to correctly handle SNOW-V

Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
---
 examples/l2fwd-crypto/main.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/examples/l2fwd-crypto/main.c b/examples/l2fwd-crypto/main.c
index a441312f55..f1a6ca8899 100644
--- a/examples/l2fwd-crypto/main.c
+++ b/examples/l2fwd-crypto/main.c
@@ -508,7 +508,8 @@ l2fwd_simple_crypto_enqueue(struct rte_mbuf *m,
 		/* For wireless algorithms, offset/length must be in bits */
 		if (cparams->cipher_algo == RTE_CRYPTO_CIPHER_SNOW3G_UEA2 ||
 				cparams->cipher_algo == RTE_CRYPTO_CIPHER_KASUMI_F8 ||
-				cparams->cipher_algo == RTE_CRYPTO_CIPHER_ZUC_EEA3) {
+				cparams->cipher_algo == RTE_CRYPTO_CIPHER_ZUC_EEA3 ||
+				cparams->cipher_algo == RTE_CRYPTO_CIPHER_SNOW_V) {
 			op->sym->cipher.data.offset = ipdata_offset << 3;
 			op->sym->cipher.data.length = data_len << 3;
 		} else {
-- 
2.43.0


  parent 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 [PATCH v2 0/5] add SNOW-V support in ipsec_mb PMD Radu Nicolau
2025-04-11 10:09 ` [PATCH v2 1/5] crypto/ipsec_mb: add support for SNOW-V Radu Nicolau
2025-04-11 10:09 ` Radu Nicolau [this message]
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-3-radu.nicolau@intel.com \
    --to=radu.nicolau@intel.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).