Re: Driver and H/W APIs Workshop at netdevconf

[Jakub Kicinski <kuba@kernel.org>]

On Mon, 6 May 2024 20:05:36 -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.
> 
> The point of the above is a list to motivate discussion based on recent
> topics.

What the point of the above list is is pretty transparent.

> > 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.

Obviously no objection to discussions about fwctl or whatever else 
you want. I am looking forward to you presenting about it "without
undue bias".

The other topics deserve their own sessions.

> > 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.