Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35;
Date:   Thu, 19 Oct 2023 09:23:46 -0700
From:   Jakub Kicinski <kuba@kernel.org>
To:     Jason Gunthorpe <jgg@nvidia.com>
Cc:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Saeed Mahameed <saeedm@nvidia.com>,
        Leon Romanovsky <leonro@nvidia.com>,
        Jiri Pirko <jiri@nvidia.com>, linux-kernel@vger.kernel.org,
        Arnd Bergmann <arnd@arndb.de>
Subject: Re: mlx5 ConnectX diagnostic misc driver
Message-ID: <20231019092346.3387fad6@kernel.org>
In-Reply-To: <20231019160145.GS3952@nvidia.com>
References: <20231019082451.785aa123@kernel.org>
        <2023101923-tried-provable-72e7@gregkh>
        <20231019160145.GS3952@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Thu, 19 Oct 2023 13:01:45 -0300 Jason Gunthorpe wrote:
> Do you have a lore link?

No, it was pitched at conferences:

Last year's LPC: https://www.youtube.com/watch?v=JGR9ZCeiW-E
This year's netconf / KR, but Saeed didn't have slides:
https://netdev.bots.linux.dev/netconf/2023/index.html

Really, you should be asking Saeed this, not me.

> Looking at Saeed's tool capability on his github it is significantly,
> but not exclusively supporting RDMA (ie drivers/infiniband), with some
> features for the mlx5 VFIO drivers, mlx5 VDPA and a bunch of lowlevel
> PCI stuff too.
> 
> Calling it a "networking device" in the sense of "it is owned only be
> netdev" is not accurate.

Yes, let's now have a pointless augment about when a NIC is a NIC
and when it's no longer a NIC because it has offloads.

My point is Saeed pitched this to networking maintainers *twice*
and then purposefully left us out of the CC list.
That is absolutely unacceptable IMO, but I'd like to consult with
others to make sure it's not just me. Please allow me some time
to do that.