netdev - Re: Driver and H/W APIs Workshop at netdevconf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZjnOfQuM2sqv377N@nanopsycho.orion>
Date: Tue, 7 May 2024 08:47:25 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: David Ahern <dsahern@...nel.org>
Cc: 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>,
	Andrew Gospodarek <andrew.gospodarek@...adcom.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

Mon, May 06, 2024 at 09:59:31PM CEST, dsahern@...nel.org 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.

I think that it would be great to discuss multi PF device with shared
resources and possilibity to represent somehow the multi-PF ASIC itself
with struct device entity of some sort.


>
>Thanks,
>