From: Raslan Darawsheh <rasland@nvidia.com>
To: Raslan Darawsheh <rasland@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Shy Shyman <shys@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] mlx5: add ConnectX-7 and Bluefield-3 device IDs
Date: Tue, 27 Oct 2020 07:25:17 +0000 [thread overview]
Message-ID: <DM6PR12MB27487AFE136B2F82366A5FE2CF160@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201026114147.9566-1-rasland@nvidia.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Raslan Darawsheh
> Sent: Monday, October 26, 2020 1:42 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Shy Shyman <shys@nvidia.com>
> Subject: [dpdk-dev] [PATCH] mlx5: add ConnectX-7 and Bluefield-3 device
> IDs
>
> This adds the ConnectX-7 and Bluefield-3 device ids to the list of
> supported Mellanox devices that run the MLX5 PMDs.
> The devices is still in development stage.
>
> Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
> ---
> drivers/common/mlx5/mlx5_common.h | 2 ++
> drivers/net/mlx5/mlx5.c | 8 ++++++++
> drivers/regex/mlx5/mlx5_regex.c | 4 ++++
> drivers/vdpa/mlx5/mlx5_vdpa.c | 8 ++++++++
> 4 files changed, 22 insertions(+)
>
> diff --git a/drivers/common/mlx5/mlx5_common.h
> b/drivers/common/mlx5/mlx5_common.h
> index ed44a45a81..93985bf2c9 100644
> --- a/drivers/common/mlx5/mlx5_common.h
> +++ b/drivers/common/mlx5/mlx5_common.h
> @@ -132,6 +132,8 @@ enum {
> PCI_DEVICE_ID_MELLANOX_CONNECTX6DXVF = 0x101e,
> PCI_DEVICE_ID_MELLANOX_CONNECTX6DXBF = 0xa2d6,
> PCI_DEVICE_ID_MELLANOX_CONNECTX6LX = 0x101f,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX7 = 0x1021,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX7BF = 0Xa2dc,
> };
>
> /* Maximum number of simultaneous unicast MAC addresses. */
> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
> index 77aeac85c5..0316253ca8 100644
> --- a/drivers/net/mlx5/mlx5.c
> +++ b/drivers/net/mlx5/mlx5.c
> @@ -2122,6 +2122,14 @@ static const struct rte_pci_id mlx5_pci_id_map[] =
> {
> RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> PCI_DEVICE_ID_MELLANOX_CONNECTX6LX)
> },
> + {
> + RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX7)
> + },
> + {
> + RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX7BF)
> + },
> {
> .vendor_id = 0
> }
> diff --git a/drivers/regex/mlx5/mlx5_regex.c
> b/drivers/regex/mlx5/mlx5_regex.c
> index 35e8ea0a9a..17590b937c 100644
> --- a/drivers/regex/mlx5/mlx5_regex.c
> +++ b/drivers/regex/mlx5/mlx5_regex.c
> @@ -254,6 +254,10 @@ static const struct rte_pci_id
> mlx5_regex_pci_id_map[] = {
> RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
>
> PCI_DEVICE_ID_MELLANOX_CONNECTX6DXBF)
> },
> + {
> + RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX7BF)
> + },
> {
> .vendor_id = 0
> }
> diff --git a/drivers/vdpa/mlx5/mlx5_vdpa.c
> b/drivers/vdpa/mlx5/mlx5_vdpa.c
> index a8f3e4b1de..2d88633bfd 100644
> --- a/drivers/vdpa/mlx5/mlx5_vdpa.c
> +++ b/drivers/vdpa/mlx5/mlx5_vdpa.c
> @@ -825,6 +825,14 @@ static const struct rte_pci_id
> mlx5_vdpa_pci_id_map[] = {
> RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
>
> PCI_DEVICE_ID_MELLANOX_CONNECTX6DXBF)
> },
> + {
> + RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX7)
> + },
> + {
> + RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX7BF)
> + },
> {
> .vendor_id = 0
> }
> --
> 2.17.1
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2020-10-27 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 11:41 Raslan Darawsheh
2020-10-26 13:39 ` Slava Ovsiienko
2020-10-27 7:25 ` Raslan Darawsheh [this message]
2020-10-29 15:26 ` Ferruh Yigit
2020-11-01 9:08 ` Raslan Darawsheh
2020-11-02 10:52 ` Ferruh Yigit
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=DM6PR12MB27487AFE136B2F82366A5FE2CF160@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=shys@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 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).