From: David Ahern <dsahern@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: 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>,
Andrew Gospodarek <andrew.gospodarek@broadcom.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: Mon, 6 May 2024 20:05:36 -0600 [thread overview]
Message-ID: <1c36d251-0218-4e9d-b6e3-0d477a5e6a02@kernel.org> (raw)
In-Reply-To: <20240506180632.2bfdc996@kernel.org>
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.
> 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.
next prev parent reply other threads:[~2024-05-07 2:05 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 [this message]
2024-05-07 2:41 ` Jakub Kicinski
2024-05-07 16:56 ` Andy Gospodarek
2024-05-07 17:02 ` David Ahern
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=1c36d251-0218-4e9d-b6e3-0d477a5e6a02@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).