linux-kernel - Re: [PATCH V4 0/5] mlx5 ConnectX control misc driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240401075003.70f5cb4b@kernel.org>
Date: Mon, 1 Apr 2024 07:50:03 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Leon Romanovsky <leon@...nel.org>
Cc: David Ahern <dsahern@...nel.org>, Greg Kroah-Hartman
 <gregkh@...uxfoundation.org>, Jason Gunthorpe <jgg@...dia.com>, Christoph
 Hellwig <hch@...radead.org>, Saeed Mahameed <saeed@...nel.org>, Arnd
 Bergmann <arnd@...db.de>, Jiri Pirko <jiri@...dia.com>, Leonid Bloch
 <lbloch@...dia.com>, Itay Avraham <itayavr@...dia.com>, Saeed Mahameed
 <saeedm@...dia.com>, Aron Silverton <aron.silverton@...cle.com>,
 linux-kernel@...r.kernel.org, "netdev@...r.kernel.org"
 <netdev@...r.kernel.org>, Andy Gospodarek <andrew.gospodarek@...adcom.com>,
 Junxian Huang <huangjunxian6@...ilicon.com>
Subject: Re: [PATCH V4 0/5] mlx5 ConnectX control misc driver

On Mon, 1 Apr 2024 15:30:03 +0300 Leon Romanovsky wrote:
> > The proposal is an attempt at a common interface and common tooling to a
> > degree but independent of any specific subsystem of which many are
> > supported by the device.
> > 
> > Your responses continue to align with the notion that because the device
> > can spit out ethernet frames, all diagnostics, debugging, configuration,
> > etc. MUST go through networking APIs.
> > 
> > You seem unwilling to acknowledge that devices can work for various use
> > cases without a netdev driver, and thus aspects of managing that device
> > should be done outside of a netdev driver.  
> 
> HNS driver is a good example of such device. It has nothing to do with
> netdev and needs common and reliable way to configure FW.

Sorry, I have a completely different reading of that thread.
Thanks for bringing it up, tho.

As I said multiple times I agree that configuring custom parameters
in RDMA is a necessity. Junxian's approach of putting such code in
the RDMA driver / subsystem is more than reasonable. Even better,
it looks like the API is fairly narrowly defined.