From: Raja Zidane <rzidane@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>
Subject: [PATCH V5] crypto/mlx5: support BF2 and ConnectX6-DX devices
Date: Thu, 11 Nov 2021 13:51:33 +0000 [thread overview]
Message-ID: <20211111135133.2367-1-rzidane@nvidia.com> (raw)
In-Reply-To: <20211110122748.34138-1-rzidane@nvidia.com>
Starting from FW version xx.32.0108. 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>
Acked-by: Tal Shnaiderman <talshn@nvidia.com>
---
V2: fixed checkpatch warning.
V3: fixed doc.
V4: fixed commit log.
V5: fixed doc.
doc/guides/cryptodevs/mlx5.rst | 11 ++++++++++-
doc/guides/rel_notes/release_21_11.rst | 1 +
drivers/crypto/mlx5/mlx5_crypto.c | 8 ++++++++
3 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/doc/guides/cryptodevs/mlx5.rst b/doc/guides/cryptodevs/mlx5.rst
index 9bd8c6fe85..af85fd2f8f 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, the internal ports in the ARMs system should also 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
@@ -155,10 +158,16 @@ Limitations
Prerequisites
-------------
+FW Prerequisites
+~~~~~~~~~~~~~~~~
+
+- xx.31.0328 for ConnectX6.
+- xx.32.0108 for ConnectX6DX and BlueField2.
+
Linux Prerequisites
~~~~~~~~~~~~~~~~~~~
-- Mellanox OFED version: **5.3**
+- Mellanox OFED version: **5.3**.
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 01923e2deb..393ff492ef 100644
--- a/doc/guides/rel_notes/release_21_11.rst
+++ b/doc/guides/rel_notes/release_21_11.rst
@@ -291,6 +291,7 @@ New Features
* **Updated Mellanox mlx5 crypto driver.**
* Added Windows support.
+ * Added support for Bluefield2 and ConnectX6-DX.
* **Updated NXP dpaa_sec crypto PMD.**
diff --git a/drivers/crypto/mlx5/mlx5_crypto.c b/drivers/crypto/mlx5/mlx5_crypto.c
index 3caa22f35f..47da3d115b 100644
--- a/drivers/crypto/mlx5/mlx5_crypto.c
+++ b/drivers/crypto/mlx5/mlx5_crypto.c
@@ -994,6 +994,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-11 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 16:22 [dpdk-dev] [PATCH] crypto/mlx5: support BF2 and ConnectX6-DX devices Raja Zidane
2021-11-07 16:26 ` Raja Zidane
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 ` Raja Zidane [this message]
2021-11-12 8:43 ` [EXT] [PATCH V5] " 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=20211111135133.2367-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 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.