From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org, abhinandan.gujjar@intel.com
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-dev] [PATCH] test/event_crypto: change the SEC cipher algo
Date: Fri, 27 Sep 2019 13:46:05 +0530 [thread overview]
Message-ID: <20190927081606.22931-2-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <20190927081606.22931-1-hemant.agrawal@nxp.com>
The existing code usages NULL as the cipher algo
for testing crypto event adapter.
DPAA1/DPAA2 do not support NULL algo. Hence changing
is to the most common algo AES-CBC, which is supported
by all crypto drivers implementing event crypto adapter.
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
app/test/test_event_crypto_adapter.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app/test/test_event_crypto_adapter.c b/app/test/test_event_crypto_adapter.c
index cff7ad61f..83f3214ca 100644
--- a/app/test/test_event_crypto_adapter.c
+++ b/app/test/test_event_crypto_adapter.c
@@ -183,7 +183,7 @@ test_op_forward_mode(uint8_t session_less)
cipher_xform.type = RTE_CRYPTO_SYM_XFORM_CIPHER;
cipher_xform.next = NULL;
- cipher_xform.cipher.algo = RTE_CRYPTO_CIPHER_NULL;
+ cipher_xform.cipher.algo = RTE_CRYPTO_CIPHER_AES_CBC;
cipher_xform.cipher.op = RTE_CRYPTO_CIPHER_OP_ENCRYPT;
op = rte_crypto_op_alloc(params.op_mpool,
@@ -373,7 +373,7 @@ test_op_new_mode(uint8_t session_less)
cipher_xform.type = RTE_CRYPTO_SYM_XFORM_CIPHER;
cipher_xform.next = NULL;
- cipher_xform.cipher.algo = RTE_CRYPTO_CIPHER_NULL;
+ cipher_xform.cipher.algo = RTE_CRYPTO_CIPHER_AES_CBC;
cipher_xform.cipher.op = RTE_CRYPTO_CIPHER_OP_ENCRYPT;
op = rte_crypto_op_alloc(params.op_mpool,
--
2.17.1
next prev parent reply other threads:[~2019-09-27 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 8:16 [dpdk-dev] [PATCH] test/event_crypto: fix mempool name Hemant Agrawal
2019-09-27 8:16 ` Hemant Agrawal [this message]
2019-09-27 10:11 ` [dpdk-dev] [PATCH] test/event_crypto: change the SEC cipher algo Gujjar, Abhinandan S
2019-09-30 8:29 ` Jerin Jacob
2019-09-27 8:16 ` [dpdk-dev] [PATCH] test/event_crypto: add check for adapter failure Hemant Agrawal
2019-09-27 10:10 ` Gujjar, Abhinandan S
2019-09-30 13:27 ` Jerin Jacob
2019-09-27 10:09 ` [dpdk-dev] [PATCH] test/event_crypto: fix mempool name Gujjar, Abhinandan S
2019-09-30 8:18 ` Jerin Jacob
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=20190927081606.22931-2-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
/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).