From: Raslan Darawsheh <rasland@nvidia.com>
To: <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <ruifeng.wang@arm.com>, Matan Azrad <matan@nvidia.com>
Subject: [PATCH v3 3/4] crypto/mlx5: add Bluefield-3 and ConnectX-7 device IDs
Date: Mon, 20 Feb 2023 10:48:26 +0200 [thread overview]
Message-ID: <20230220084827.3317796-4-rasland@nvidia.com> (raw)
In-Reply-To: <20230220084827.3317796-1-rasland@nvidia.com>
This adds the Bluefield-3 and ConnectX-7 device IDs to the
list of supported NVIDIA devices that run the MLX5 compress PMD.
The BlueField-3 device is still in development stage.
Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
---
drivers/crypto/mlx5/mlx5_crypto.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/crypto/mlx5/mlx5_crypto.c b/drivers/crypto/mlx5/mlx5_crypto.c
index 2988642857..5267f48c1e 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_BLUEFIELD2)
},
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_CONNECTX7)
+ },
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_BLUEFIELD3)
+ },
{
.vendor_id = 0
}
--
2.25.1
next prev parent reply other threads:[~2023-02-20 8:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 13:59 [PATCH 1/4] config/arm: add NVIDIA BlueField-3 platform Raslan Darawsheh
2023-02-16 13:59 ` [PATCH 2/4] crypto/mlx5: add Bluefield-3 and ConnectX-7 device IDs Raslan Darawsheh
2023-02-16 13:59 ` [PATCH 3/4] doc: update supported devices for NVIDIA NICs Raslan Darawsheh
2023-02-16 13:59 ` [PATCH 4/4] mlx: update PCI device IDs names for NVIDIA BlueField NICs Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 0/4] support NVIDIA Bluefield-3 device Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 1/4] mlx: update PCI device IDs names for NVIDIA BlueField NICs Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 2/4] config/arm: add NVIDIA BlueField-3 platform Raslan Darawsheh
2023-02-20 2:50 ` Ruifeng Wang
2023-02-20 8:42 ` Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 3/4] crypto/mlx5: add Bluefield-3 and ConnectX-7 device IDs Raslan Darawsheh
2023-02-16 14:04 ` [PATCH v2 4/4] doc: update supported devices for NVIDIA NICs Raslan Darawsheh
2023-02-20 8:48 ` [PATCH v3 0/4] support NVIDIA Bluefield-3 device Raslan Darawsheh
2023-02-20 8:48 ` [PATCH v3 1/4] mlx: update PCI device IDs names for NVIDIA BlueField NICs Raslan Darawsheh
2023-02-20 8:48 ` [PATCH v3 2/4] config/arm: add NVIDIA BlueField-3 platform Raslan Darawsheh
2023-02-20 8:48 ` Raslan Darawsheh [this message]
2023-02-20 8:48 ` [PATCH v3 4/4] doc: update supported devices for NVIDIA NICs Raslan Darawsheh
2023-02-20 10:40 ` [PATCH v3 0/4] support NVIDIA Bluefield-3 device Thomas Monjalon
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=20230220084827.3317796-4-rasland@nvidia.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).