[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240402224632.GT946323@nvidia.com>
Date: Tue, 2 Apr 2024 19:46:32 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Leon Romanovsky <leon@...nel.org>, David Ahern <dsahern@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
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 Tue, Apr 02, 2024 at 02:36:07PM -0700, Jakub Kicinski wrote:
> > FWIW, I've been trying to push RDMA away from driver created sysfs for
> > a while now. Aside from the API complexity, implementations have
> > messed up using the sysfs APIs and resulted in some significant
> > problems :(
>
> Sure, agreed, but off-topic.
It is not - I don't want a huge amount of sysfs in drivers to replace
what fwctl will do for pretty solid technical reasons.
I do object, as snarky as I was, to you saying RDMA should take on a
whole bunch of read/write sysfs in drivers that netdev would not
accept as a "reasonable" direction.
Jason
Powered by blists - more mailing lists