From: Raslan Darawsheh <rasland@nvidia.com>
To: <dev@dpdk.org>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: [PATCH] common/mlx5: add ConnectX-10 NVLink-C2C device ID
Date: Mon, 22 Jun 2026 11:01:49 +0300 [thread overview]
Message-ID: <20260622080149.11394-1-rasland@nvidia.com> (raw)
This adds the ConnectX-10 NVLink-C2C device ID to the list of
NVIDIA devices that run the mlx5 drivers.
The device is still in development stage.
Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
---
drivers/common/mlx5/mlx5_common.h | 1 +
drivers/crypto/mlx5/mlx5_crypto.c | 4 ++++
drivers/net/mlx5/mlx5.c | 4 ++++
3 files changed, 9 insertions(+)
diff --git a/drivers/common/mlx5/mlx5_common.h b/drivers/common/mlx5/mlx5_common.h
index 3e66c9e6c8..3767020823 100644
--- a/drivers/common/mlx5/mlx5_common.h
+++ b/drivers/common/mlx5/mlx5_common.h
@@ -157,6 +157,7 @@ enum {
PCI_DEVICE_ID_MELLANOX_CONNECTX9 = 0x1025,
PCI_DEVICE_ID_MELLANOX_BLUEFIELD4 = 0xa2df,
PCI_DEVICE_ID_MELLANOX_CONNECTX10 = 0x1027,
+ PCI_DEVICE_ID_MELLANOX_CONNECTX10C2C = 0x2101,
};
/* Maximum number of simultaneous unicast MAC addresses. */
diff --git a/drivers/crypto/mlx5/mlx5_crypto.c b/drivers/crypto/mlx5/mlx5_crypto.c
index dd0aabb6d7..c9aa858a54 100644
--- a/drivers/crypto/mlx5/mlx5_crypto.c
+++ b/drivers/crypto/mlx5/mlx5_crypto.c
@@ -499,6 +499,10 @@ static const struct rte_pci_id mlx5_crypto_pci_id_map[] = {
RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
PCI_DEVICE_ID_MELLANOX_CONNECTX10)
},
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_CONNECTX10C2C)
+ },
{
.vendor_id = 0
}
diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
index 61c26d1206..3fa38694e5 100644
--- a/drivers/net/mlx5/mlx5.c
+++ b/drivers/net/mlx5/mlx5.c
@@ -3936,6 +3936,10 @@ static const struct rte_pci_id mlx5_pci_id_map[] = {
RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
PCI_DEVICE_ID_MELLANOX_CONNECTX10)
},
+ {
+ RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
+ PCI_DEVICE_ID_MELLANOX_CONNECTX10C2C)
+ },
{
.vendor_id = 0
}
--
2.53.0
next reply other threads:[~2026-06-22 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:01 Raslan Darawsheh [this message]
2026-06-24 9:35 ` [PATCH] common/mlx5: add ConnectX-10 NVLink-C2C device ID Raslan Darawsheh
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=20260622080149.11394-1-rasland@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@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.