[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZjpdV2l7VckPz-jj@C02YVCJELVCG.dhcp.broadcom.net>
Date: Tue, 7 May 2024 12:56:55 -0400
From: Andy Gospodarek <andrew.gospodarek@...adcom.com>
To: David Ahern <dsahern@...nel.org>
Cc: Jakub Kicinski <kuba@...nel.org>,
Jacob Keller <jacob.e.keller@...el.com>,
Alexander Lobakin <aleksander.lobakin@...el.com>,
Saeed Mahameed <saeedm@...dia.com>,
Tariq Toukan <tariqt@...dia.com>, Jason Gunthorpe <jgg@...dia.com>,
Andrew Gospodarek <andrew.gospodarek@...adcom.com>,
"michael.chan@...adcom.com" <michael.chan@...adcom.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...dia.com>,
Alexander Duyck <alexander.duyck@...il.com>
Subject: Re: Driver and H/W APIs Workshop at netdevconf
On Mon, May 06, 2024 at 08:05:36PM -0600, David Ahern wrote:
> On 5/6/24 7:06 PM, Jakub Kicinski wrote:
> > On Mon, 6 May 2024 13:59:31 -0600 David Ahern wrote:
> >> Suggested topics based on recent netdev threads include
> >> - devlink - extensions, shortcomings, ...
> >> - extension to memory pools
> >> - new APIs for managing queues
> >> - challenges of netdev / IB co-existence (e.g., driven by AI workloads)
> >> - fwctl - a proposal for direct firmware access
> >
> > Memory pools and queue API are more of stack features.
>
> That require driver support, no? e.g., There is no way that queue API is
> going to work with the Enfabrica device without driver support.
I defintely think that there should be a consumer of the queue API
before it lands upstream, but if it cannot work without a
driver/hardware support that seems a bit odd.
Maybe I've missed it on the list, but do you have something you can
share about this proposed queue API?
> The point of the above is a list to motivate discussion based on recent
> topics.
>
>
> > Please leave them out of your fwctl session.
>
> fwctl is a discussion item not tied to anything else; let's not conflat
> topics here. That it is even on this list is because you brought netdev
> into a discussion that is not netdev related. Given that, let's give it
> proper daylight any topic deserves without undue bias and letting it
> dominate the bigger picture.
>
> >
> > Aren't people who are actually working on those things submitting
> > talks or hosting better scoped discussions? It appears you haven't
> > CCed any of them..
>
> I have no idea. I started with a list of well known driver contacts and
> cc'ed netdev with an explicit statement that it is open to all.
Powered by blists - more mailing lists