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.nico...@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

Reply via email to