From: Radu Nicolau <radu.nicolau@intel.com>
To: dev@dpdk.org
Cc: Radu Nicolau <radu.nicolau@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Beilei Xing <beilei.xing@intel.com>
Subject: [PATCH] net/iavf: remove contrains for AEAD IV and AAD size
Date: Fri, 17 Feb 2023 11:52:45 +0000 [thread overview]
Message-ID: <20230217115246.72626-1-radu.nicolau@intel.com> (raw)
Because of incosistencies between IPsec library and sample app
implementations for inline crypto remove IV and AAD size constrains
from the advertised crypto capabilities
Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
---
drivers/net/iavf/iavf_ipsec_crypto.c | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/net/iavf/iavf_ipsec_crypto.c b/drivers/net/iavf/iavf_ipsec_crypto.c
index 08a80137e5..082948b61f 100644
--- a/drivers/net/iavf/iavf_ipsec_crypto.c
+++ b/drivers/net/iavf/iavf_ipsec_crypto.c
@@ -1305,13 +1305,14 @@ update_aead_capabilities(struct rte_cryptodev_capabilities *scap,
capability->aead.key_size.max = acap->max_key_size;
capability->aead.key_size.increment = acap->inc_key_size;
- capability->aead.aad_size.min = acap->min_aad_size;
- capability->aead.aad_size.max = acap->max_aad_size;
- capability->aead.aad_size.increment = acap->inc_aad_size;
-
- capability->aead.iv_size.min = acap->min_iv_size;
- capability->aead.iv_size.max = acap->max_iv_size;
- capability->aead.iv_size.increment = acap->inc_iv_size;
+ /* remove constrains for aead and iv length */
+ capability->aead.aad_size.min = 0;
+ capability->aead.aad_size.max = 65535;
+ capability->aead.aad_size.increment = 1;
+
+ capability->aead.iv_size.min = 0;
+ capability->aead.iv_size.max = 65535;
+ capability->aead.iv_size.increment = 1;
capability->aead.digest_size.min = acap->min_digest_size;
capability->aead.digest_size.max = acap->max_digest_size;
--
2.25.1
next reply other threads:[~2023-02-17 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 11:52 Radu Nicolau [this message]
2023-02-21 0:33 ` Zhang, Qi Z
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=20230217115246.72626-1-radu.nicolau@intel.com \
--to=radu.nicolau@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@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).