From: Jakub Kicinski <kuba@kernel.org>
To: David Ahern <dsahern@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 18:06:32 -0700 [thread overview]
Message-ID: <20240506180632.2bfdc996@kernel.org> (raw)
In-Reply-To: <c4ae5f08-11f2-48f7-9c2a-496173f3373e@kernel.org>
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.
Please leave them out of your fwctl session.
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..
next prev parent reply other threads:[~2024-05-07 1:06 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 [this message]
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
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=20240506180632.2bfdc996@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexander.duyck@gmail.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=dsahern@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=jgg@nvidia.com \
--cc=jiri@nvidia.com \
--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).