[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zjpo3u7gu8_y0jaU@C02YVCJELVCG.dhcp.broadcom.net>
Date: Tue, 7 May 2024 13:46:06 -0400
From: Andy Gospodarek <andrew.gospodarek@...adcom.com>
To: David Ahern <dsahern@...nel.org>
Cc: Andy Gospodarek <andrew.gospodarek@...adcom.com>,
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>,
"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 Tue, May 07, 2024 at 11:02:05AM -0600, David Ahern wrote:
> On 5/7/24 10:56 AM, Andy Gospodarek wrote:
> >>
> >> 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?
> >
>
> commit 087b24de5c825c53f15a9481b94f757223c20610
> Author: Mina Almasry <almasrymina@...gle.com>
> Date: Wed May 1 23:25:40 2024 +0000
>
> queue_api: define queue api
>
> This API enables the net stack to reset the queues used for devmem TCP.
>
>
> and then gve support for it:
>
> commit c93462b914dbf46b0c0256f7784cc79f7c368e45
> Author: Shailend Chand <shailend@...gle.com>
> Date: Wed May 1 23:25:49 2024 +0000
>
> gve: Implement queue api
>
> The new netdev queue api is implemented for gve.
Thanks, good news is I'm aware of those. I guess I read your statement
a little differently than you probably intended....
Good topic as there are some more things that are worth considering based on
driver/HW nuances that are likely going to be diff for each vendor.
Powered by blists - more mailing lists