From: Tejasree Kondoj <ktejasree@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>, Radu Nicolau <radu.nicolau@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>, <dev@dpdk.org>
Subject: [PATCH v3] examples/ipsec-secgw: set AES-CTR IV length to 16
Date: Thu, 23 Feb 2023 21:13:06 +0530 [thread overview]
Message-ID: <20230223154306.2807523-1-ktejasree@marvell.com> (raw)
In-Reply-To: <20221215054211.1919093-1-ktejasree@marvell.com>
Set AES-CTR IV length to 16 which includes
8B per packet IV, 4B nonce and 4B counter
as populated in datapath.
Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com>
---
v3:
* Changed IV length in initialization.
v2:
* Rebased v1
examples/ipsec-secgw/sa.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/examples/ipsec-secgw/sa.c b/examples/ipsec-secgw/sa.c
index 7da9444a7b..eb485e6b2b 100644
--- a/examples/ipsec-secgw/sa.c
+++ b/examples/ipsec-secgw/sa.c
@@ -96,7 +96,10 @@ const struct supported_cipher_algo cipher_algos[] = {
{
.keyword = "aes-128-ctr",
.algo = RTE_CRYPTO_CIPHER_AES_CTR,
- .iv_len = 8,
+ /* iv_len includes 8B per packet IV, 4B nonce
+ * and 4B counter
+ */
+ .iv_len = 16,
.block_size = 4,
.key_len = 20
},
--
2.25.1
next prev parent reply other threads:[~2023-02-23 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 3:58 [PATCH] " Tejasree Kondoj
2022-12-15 5:42 ` [PATCH v2] " Tejasree Kondoj
2023-02-01 14:16 ` Akhil Goyal
2023-02-01 14:37 ` Nicolau, Radu
2023-02-21 16:37 ` [EXT] " Tejasree Kondoj
2023-02-22 9:56 ` Nicolau, Radu
2023-02-22 13:43 ` Akhil Goyal
2023-02-23 15:43 ` Tejasree Kondoj [this message]
2023-02-27 17:45 ` [PATCH v3] " 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=20230223154306.2807523-1-ktejasree@marvell.com \
--to=ktejasree@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=radu.nicolau@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).