[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240607184316.1acdb3fd@kernel.org>
Date: Fri, 7 Jun 2024 18:43:16 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Andrew Lunn <andrew@...n.ch>, David Ahern <dsahern@...nel.org>, Jason
Gunthorpe <jgg@...dia.com>, Dan Williams <dan.j.williams@...el.com>,
Jonathan Corbet <corbet@....net>, Itay Avraham <itayavr@...dia.com>, Leon
Romanovsky <leon@...nel.org>, linux-doc@...r.kernel.org,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org, Paolo Abeni
<pabeni@...hat.com>, Saeed Mahameed <saeedm@...dia.com>, Tariq Toukan
<tariqt@...dia.com>, Andy Gospodarek <andrew.gospodarek@...adcom.com>, Aron
Silverton <aron.silverton@...cle.com>, Christoph Hellwig
<hch@...radead.org>, Jiri Pirko <jiri@...dia.com>, Leonid Bloch
<lbloch@...dia.com>, Leon Romanovsky <leonro@...dia.com>,
linux-cxl@...r.kernel.org, patches@...ts.linux.dev
Subject: Re: [PATCH 0/8] Introduce fwctl subystem
On Fri, 7 Jun 2024 15:34:48 +0200 Jiri Pirko wrote:
> >For bigger, single purpose devices, it is just a switch, there is less
> >inconvenience of using just one vendor SDK, on top of the vendor
> >proscribed kernel.
>
> I'm aware of what you wrote and undertand it. I just thought Jakub's
> mixed experience is about the APIs more than the politics behind vedors
> adoptation process..
Not the API / implementation, just that the adoption is limited.
The benefits of using a standard Linux approach is outweighed by
the large pool of talent with experience programming using the SDK
of *the* vendor.
Powered by blists - more mailing lists