[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZXniAwBwtF5hmOuq@infradead.org>
Date: Wed, 13 Dec 2023 08:55:31 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Saeed Mahameed <saeed@...nel.org>
Cc: Aron Silverton <aron.silverton@...cle.com>,
Jakub Kicinski <kuba@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jason Gunthorpe <jgg@...dia.com>,
David Ahern <dsahern@...nel.org>,
Arnd Bergmann <arnd@...db.de>,
Leon Romanovsky <leonro@...dia.com>,
Jiri Pirko <jiri@...dia.com>, Leonid Bloch <lbloch@...dia.com>,
Itay Avraham <itayavr@...dia.com>,
linux-kernel@...r.kernel.org, Saeed Mahameed <saeedm@...dia.com>
Subject: Re: [PATCH V3 2/5] misc: mlx5ctl: Add mlx5ctl misc driver
On Thu, Dec 07, 2023 at 10:54:02AM -0800, Saeed Mahameed wrote:
> Also I would like to repeat, this is not touching netdev, netdev's policies
> do not apply to the greater kernel or RDMA, and we have use cases with
> pure-infiniband/DPU/FPGA cards that have no netdev at all, or other cases
> with pur virtio instances, and much more.
Yes. I mean just about every complex block driver has some kind of
vendor spcific tooling for debugging, statistics, etc. Trying to deny
it just because one function expose by a device is a network device is
even more silly than disallowing it for pure net devices (which already
tend to be complex beasts).
Powered by blists - more mailing lists