From: Raja Zidane <rzidane@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>
Subject: [dpdk-dev] [PATCH] crypto/mlx5: support BF2 and ConnectX6-DX devices
Date: Sun, 7 Nov 2021 16:26:38 +0000 [thread overview]
Message-ID: <20211107162638.1583-1-rzidane@nvidia.com> (raw)
In-Reply-To: <20211107162202.40701-1-rzidane@nvidia.com>
Starting from MLNX_OFED 5.5. version, the BlueField2 and ConnextX6-DX
adapters support crypto operations.
Add them to the supported PCI devices list.
Signed-off-by: Raja Zidane <rzidane@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>
---
dependant on https://patchwork.dpdk.org/project/dpdk/cover/20211104124929.24899-1-rzidane@nvidia.com/
V2: fix checkpatch warning.
doc/guides/cryptodevs/mlx5.rst | 6 +++++-
doc/guides/rel_notes/release_21_11.rst | 4 ++++
drivers/crypto/mlx5/mlx5_crypto.c | 8 ++++++++
3 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/doc/guides/cryptodevs/mlx5.rst b/doc/guides/cryptodevs/mlx5.rst
index 9bd8c6fe85..4ca0f7e5ea 100644
--- a/doc/guides/cryptodevs/mlx5.rst
+++ b/doc/guides/cryptodevs/mlx5.rst
@@ -88,6 +88,7 @@ The mlxreg dedicated tool should be used as follows:
should not be specified.
All the device ports should set it in order to move to operational mode.
+ For BlueField2, also the internal ports in the ARMs system should be set.
- Query CRYPTO_OPERATIONAL register to make sure the device is in Operational
mode.
@@ -141,6 +142,8 @@ Supported NICs
--------------
* Mellanox\ |reg| ConnectX\ |reg|-6 200G MCX654106A-HCAT (2x200G)
+* Mellanox\ |reg| BlueField 2 SmartNIC
+* Mellanox\ |reg| ConnectX\ |reg|-6DX
Limitations
@@ -158,7 +161,8 @@ Prerequisites
Linux Prerequisites
~~~~~~~~~~~~~~~~~~~
-- Mellanox OFED version: **5.3**
+- Mellanox OFED version: starts at 5.3 for ConnectX6.
+ Mellanox OFED version: 5.5 for ConnectX6DX and BF2.
see :doc:`../../nics/mlx5` guide for more Mellanox OFED details.
- Compilation can be done also with rdma-core v15+.
diff --git a/doc/guides/rel_notes/release_21_11.rst b/doc/guides/rel_notes/release_21_11.rst
index 9bf4479002..490a8859d7 100644
--- a/doc/guides/rel_notes/release_21_11.rst
+++ b/doc/guides/rel_notes/release_21_11.rst
@@ -401,6 +401,10 @@ New Features
overruns in C/C++ programs, and other similar errors, as well as
printing out detailed debug information whenever an error is detected.
+* **Updated mlx5 crypto driver.**
+
+ * Added support for BF2.
+ * Added support for CX6DX.
Removed Items
-------------
diff --git a/drivers/crypto/mlx5/mlx5_crypto.c b/drivers/crypto/mlx5/mlx5_crypto.c
index 038526c023..316cb46ebf 100644
--- a/drivers/crypto/mlx5/mlx5_crypto.c
+++ b/drivers/crypto/mlx5/mlx5_crypto.c
@@ -1034,6 +1034,14 @@ static const struct rte_pci_id mlx5_crypto_pci_id_map[] = {
RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
PCI_DEVICE_ID_MELLANOX_CONNECTX6)
},
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_CONNECTX6DX)
+ },
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_CONNECTX6DXBF)
+ },
{
.vendor_id = 0
}
--
2.17.1
next prev parent reply other threads:[~2021-11-07 16:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 16:22 Raja Zidane
2021-11-07 16:26 ` Raja Zidane [this message]
2021-11-07 17:29 ` [dpdk-dev] [PATCH V2] " Raja Zidane
2021-11-07 17:44 ` Thomas Monjalon
2021-11-07 19:03 ` Tal Shnaiderman
2021-11-08 13:18 ` [dpdk-dev] [PATCH V3] " Raja Zidane
2021-11-08 14:03 ` Tal Shnaiderman
2021-11-10 12:27 ` [dpdk-dev] [PATCH V4] " Raja Zidane
2021-11-10 12:47 ` Tal Shnaiderman
2021-11-11 11:11 ` [EXT] " Akhil Goyal
2021-11-11 13:51 ` [PATCH V5] " Raja Zidane
2021-11-12 8:43 ` [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=20211107162638.1583-1-rzidane@nvidia.com \
--to=rzidane@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.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).