From: Shahaf Shuler <shahafs@mellanox.com>
To: Wisam Monther <wisamm@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: add ConnectX6 support
Date: Mon, 31 Dec 2018 07:28:07 +0000 [thread overview]
Message-ID: <DB7PR05MB44264CD06DC392B156469772C3B20@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1546179401-29391-1-git-send-email-wisamm@mellanox.com>
Sunday, December 30, 2018 4:17 PM, Wisam Monther:
> Subject: [PATCH] net/mlx5: add ConnectX6 support
Name should be ConnectX-6.
>
> Signed-off-by: Wisam Jaddo <wisamm@mellanox.com>
> ---
> drivers/net/mlx5/mlx5.c | 4 ++++
> drivers/net/mlx5/mlx5.h | 1 +
> 2 files changed, 5 insertions(+)
Need to update also the rst file. See example in https://www.mail-archive.com/dev@dpdk.org/msg101529.html
ConnectX-6 is of course 200G.
>
> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c index
> 9e5cab1..dcabeb1 100644
> --- a/drivers/net/mlx5/mlx5.c
> +++ b/drivers/net/mlx5/mlx5.c
> @@ -1586,6 +1586,10 @@ static const struct rte_pci_id mlx5_pci_id_map[] = {
> PCI_DEVICE_ID_MELLANOX_CONNECTX5BFVF)
> },
> {
> + RTE_PCI_DEVICE(PCI_VENDOR_ID_MELLANOX,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX6)
> + },
> + {
I assume we want also to add the ConnectX-6 VF, right?
> .vendor_id = 0
> }
> };
> diff --git a/drivers/net/mlx5/mlx5.h b/drivers/net/mlx5/mlx5.h index
> b2fe5cb..c7efc3c 100644
> --- a/drivers/net/mlx5/mlx5.h
> +++ b/drivers/net/mlx5/mlx5.h
> @@ -52,6 +52,7 @@ enum {
> PCI_DEVICE_ID_MELLANOX_CONNECTX5EXVF = 0x101a,
> PCI_DEVICE_ID_MELLANOX_CONNECTX5BF = 0xa2d2,
> PCI_DEVICE_ID_MELLANOX_CONNECTX5BFVF = 0xa2d3,
> + PCI_DEVICE_ID_MELLANOX_CONNECTX6 = 0x101b,
> };
>
> /** Switch information returned by mlx5_nl_switch_info(). */
> --
> 2.7.4
prev parent reply other threads:[~2018-12-31 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 14:16 Wisam Monther
2018-12-31 7:28 ` Shahaf Shuler [this message]
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=DB7PR05MB44264CD06DC392B156469772C3B20@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=wisamm@mellanox.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).