From: Shijith Thotton <sthotton@marvell.com>
To: <dev@dpdk.org>
Cc: Shijith Thotton <sthotton@marvell.com>,
Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Anoob Joseph <anoobj@marvell.com>
Subject: [dpdk-dev] [PATCH v1] eventdev: fix case to initiate crypto adapter service
Date: Fri, 9 Apr 2021 12:38:09 +0530 [thread overview]
Message-ID: <20210409070809.456444-1-sthotton@marvell.com> (raw)
Initiate software crypto adapter service, only if hardware capabilities
are not reported.
Case 1.a. OP_FORWARD mode -> HW Dequeue + SW enqueue, should also check
OP_FORWARD capability is not supported by the PMD to initiate service.
Fixes: 7901eac3409a ("eventdev: add crypto adapter implementation")
Signed-off-by: Shijith Thotton <sthotton@marvell.com>
---
lib/librte_eventdev/rte_event_crypto_adapter.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_eventdev/rte_event_crypto_adapter.c b/lib/librte_eventdev/rte_event_crypto_adapter.c
index d903cdd48..e1d38d383 100644
--- a/lib/librte_eventdev/rte_event_crypto_adapter.c
+++ b/lib/librte_eventdev/rte_event_crypto_adapter.c
@@ -861,6 +861,7 @@ rte_event_crypto_adapter_queue_pair_add(uint8_t id,
* b. OP_NEW mode -> SW Dequeue
*/
if ((cap & RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_OP_NEW &&
+ !(cap & RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_OP_FWD) &&
adapter->mode == RTE_EVENT_CRYPTO_ADAPTER_OP_FORWARD) ||
(!(cap & RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_OP_NEW) &&
!(cap & RTE_EVENT_CRYPTO_ADAPTER_CAP_INTERNAL_PORT_OP_FWD) &&
--
2.25.1
next reply other threads:[~2021-04-09 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 7:08 Shijith Thotton [this message]
2021-04-12 7:30 ` [dpdk-dev] [PATCH v1] eventdev: fix case to initiate crypto adapter service Jerin Jacob
2021-04-12 8:53 ` [dpdk-dev] [PATCH v2] " Shijith Thotton
2021-04-13 4:08 ` Gujjar, Abhinandan S
2021-04-13 7:51 ` Shijith Thotton
2021-04-14 7:06 ` Gujjar, Abhinandan S
2021-04-17 17:24 ` 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=20210409070809.456444-1-sthotton@marvell.com \
--to=sthotton@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.