From: David Ahern <dsahern@kernel.org>
To: Andy Gospodarek <andrew.gospodarek@broadcom.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Jacob Keller <jacob.e.keller@intel.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
"michael.chan@broadcom.com" <michael.chan@broadcom.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jiri Pirko <jiri@nvidia.com>,
Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: Driver and H/W APIs Workshop at netdevconf
Date: Tue, 7 May 2024 11:02:05 -0600 [thread overview]
Message-ID: <12ab765e-d808-4bbe-a2d3-87a8c5fb8b54@kernel.org> (raw)
In-Reply-To: <ZjpdV2l7VckPz-jj@C02YVCJELVCG.dhcp.broadcom.net>
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@google.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@google.com>
Date: Wed May 1 23:25:49 2024 +0000
gve: Implement queue api
The new netdev queue api is implemented for gve.
next prev parent reply other threads:[~2024-05-07 17:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 19:59 Driver and H/W APIs Workshop at netdevconf David Ahern
2024-05-07 1:06 ` Jakub Kicinski
2024-05-07 2:05 ` David Ahern
2024-05-07 2:41 ` Jakub Kicinski
2024-05-07 16:56 ` Andy Gospodarek
2024-05-07 17:02 ` David Ahern [this message]
2024-05-07 17:46 ` Andy Gospodarek
2024-05-07 18:17 ` Mina Almasry
2024-05-07 19:21 ` Jakub Kicinski
2024-05-07 20:40 ` Mina Almasry
2024-05-07 20:58 ` Jakub Kicinski
2024-05-07 20:47 ` Nambiar, Amritha
2024-05-08 1:58 ` David Ahern
2024-05-07 6:47 ` Jiri Pirko
2024-05-08 16:29 ` Keller, Jacob E
2024-06-16 18:15 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12ab765e-d808-4bbe-a2d3-87a8c5fb8b54@kernel.org \
--to=dsahern@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=jacob.e.keller@intel.com \
--cc=jgg@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).