From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, fiona.trahe@intel.com,
roy.fan.zhang@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [dpdk-dev] [PATCH 2/2] crypto/qat: fix asymmetric crypto pmd create on gen3
Date: Wed, 28 Jul 2021 17:18:31 +0100 [thread overview]
Message-ID: <20210728161831.6807-3-arkadiuszx.kusztal@intel.com> (raw)
In-Reply-To: <20210728161831.6807-1-arkadiuszx.kusztal@intel.com>
This patch disables asymmetric crypto pmd on gen3 devices.
Fixes: 1f5e4053f9b4 ("common/qat: support GEN3 devices")
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
drivers/crypto/qat/qat_asym_pmd.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/crypto/qat/qat_asym_pmd.c b/drivers/crypto/qat/qat_asym_pmd.c
index d4680c3847..4891766471 100644
--- a/drivers/crypto/qat/qat_asym_pmd.c
+++ b/drivers/crypto/qat/qat_asym_pmd.c
@@ -255,6 +255,10 @@ qat_asym_dev_create(struct qat_pci_device *qat_pci_dev,
QAT_LOG(ERR, "Asymmetric crypto PMD not supported on QAT 4xxx");
return -(EFAULT);
}
+ if (qat_pci_dev->qat_dev_gen == QAT_GEN3) {
+ QAT_LOG(ERR, "Asymmetric crypto PMD not supported on QAT c4xxx");
+ return -(EFAULT);
+ }
snprintf(name, RTE_CRYPTODEV_NAME_MAX_LEN, "%s_%s",
qat_pci_dev->name, "asym");
QAT_LOG(DEBUG, "Creating QAT ASYM device %s\n", name);
--
2.30.2
next prev parent reply other threads:[~2021-07-28 16:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 16:18 [dpdk-dev] [PATCH 0/2] drivers/qat: fix handling of unsupported services Arek Kusztal
2021-07-28 16:18 ` [dpdk-dev] [PATCH 1/2] drivers/qat: fix wrong return value for invalid service Arek Kusztal
2021-07-29 8:58 ` Zhang, Roy Fan
2021-07-30 19:18 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-31 9:29 ` Thomas Monjalon
2021-07-28 16:18 ` Arek Kusztal [this message]
2021-07-29 8:57 ` [dpdk-dev] [PATCH 2/2] crypto/qat: fix asymmetric crypto pmd create on gen3 Zhang, Roy Fan
2021-07-30 19:19 ` [dpdk-dev] [EXT] " Akhil Goyal
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=20210728161831.6807-3-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=gakhil@marvell.com \
--cc=roy.fan.zhang@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).