aboutsummaryrefslogtreecommitdiff
path: root/platform/linux-dpdk
diff options
context:
space:
mode:
authorJanne Peltonen <janne.peltonen@nokia.com>2023-03-21 11:26:06 +0200
committerMatias Elo <matias.elo@nokia.com>2023-03-23 08:55:21 +0200
commitbb2e517d0cef5a44ab5322f286201306c1d7a502 (patch)
tree5fa4518f8a2b53f5d1a98c420d635b18f53a5512 /platform/linux-dpdk
parentdf7fa2e0156b99fcd1c1c0d431514ced382024c4 (diff)
linux-dpdk: crypto: do not use broken SGL of the aesni_mb device
In DPDK 22.11 the aesni_mb crypto device advertises SGL capabilities but the SGL support does not work correctly. ODP validation tests detect the problems. Work around the issue by marking aesni_mb not supporting chained buffers regardless of what it claims. Signed-off-by: Janne Peltonen <janne.peltonen@nokia.com> Reviewed-by: Matias Elo <matias.elo@nokia.com>
Diffstat (limited to 'platform/linux-dpdk')
-rw-r--r--platform/linux-dpdk/odp_crypto.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/platform/linux-dpdk/odp_crypto.c b/platform/linux-dpdk/odp_crypto.c
index 61d4a12e4..c1cac8566 100644
--- a/platform/linux-dpdk/odp_crypto.c
+++ b/platform/linux-dpdk/odp_crypto.c
@@ -1266,6 +1266,10 @@ static int chained_bufs_ok(const odp_crypto_session_param_t *param,
*/
if (dev_info.driver_name &&
+ !strcmp(dev_info.driver_name, "crypto_aesni_mb"))
+ chained_bufs_ok = 0;
+
+ if (dev_info.driver_name &&
!strcmp(dev_info.driver_name, "crypto_aesni_gcm") &&
param->auth_alg == ODP_AUTH_ALG_AES_GMAC)
chained_bufs_ok = 0;