netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: 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>
Cc: Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: Driver and H/W APIs Workshop at netdevconf
Date: Sun, 16 Jun 2024 12:15:53 -0600	[thread overview]
Message-ID: <ea1747c2-896e-4ea0-afb3-a0de3ea53ccc@kernel.org> (raw)
In-Reply-To: <c4ae5f08-11f2-48f7-9c2a-496173f3373e@kernel.org>

On 5/6/24 1:59 PM, David Ahern wrote:
> Alex Duyck and I are co-chairing the "Driver and H/W APIs Workshop" at
> netdevconf in July.
> 
> The workshop is a forum for discussing issues related to driver
> development and APIs (user and kernel) for configuring, monitoring and
> debugging hardware. Discussion will be open to anyone to present, though
> speakers will need to submit topics ahead of time.
> 
> 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
> 
> 
> Please let us know if you have a topic that you would like to discuss
> along with a time estimate.
> 
> Thanks,

Reminder about this workshop at the upcoming netdevconf. It is scheduled
for Tuesday, July 16, at 10 a.m. PDT. If anyone has topics to discuss,
please let Alex and I know.

Current responses:
- Jiri Pirko / Jacob Keller
  + multi PF device with shared resources

- Amritha Nambiar
  + NAPI config for queue-set API?
  + devlink-extensions

I have a couple of topics - uapis and possibly fwctl.

      parent reply	other threads:[~2024-06-16 18:15 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
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 [this message]

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=ea1747c2-896e-4ea0-afb3-a0de3ea53ccc@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=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).