DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@intel.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: Sun, 1 Nov 2020 09:08:20 +0000
Message-ID: <BN7PR12MB2737D0E573E074FB7B6E5E78CF130@BN7PR12MB2737.namprd12.prod.outlook.com> (raw)
In-Reply-To: <d6e1fcce-67d7-bd5d-92d9-3af956bb4a3c@intel.com>

Hi Ferruh,

> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Thursday, October 29, 2020 5:26 PM
> To: Raslan Darawsheh <rasland@nvidia.com>; 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
> On 10/26/2020 11:41 AM, Raslan Darawsheh wrote:
> > 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.
> >
> I assume you don't want to add these new device support to the
> documentation or
> to the web page, but what do you think adding it to the driver
> documentation
> with this device under development note, or experimental support etc?
It's about that we haven't tried the PMD with these NIC's yet, so announcing that it has support for them
without knowing that we don't really have any issues (even 0 level issue) I don't think its OK to add such documentation.

I think once we'll have the proper testing done for them, we can add them to all necessary documentations

> > Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
> <...>

Kindest regards,
Raslan Darawsheh

  reply	other threads:[~2020-11-01  9:08 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
2020-10-29 15:26 ` Ferruh Yigit
2020-11-01  9:08   ` Raslan Darawsheh [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BN7PR12MB2737D0E573E074FB7B6E5E78CF130@BN7PR12MB2737.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=matan@nvidia.com \
    --cc=shys@nvidia.com \
    --cc=viacheslavo@nvidia.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git