netdev - [ANN] netdev call

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20240617083955.1039b2e3@kernel.org>
Date: Mon, 17 Jun 2024 08:39:55 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: netdev@...r.kernel.org, netdev-driver-reviewers@...r.kernel.org
Cc: Shannon Nelson <shannon.nelson@....com>, Vladimir Oltean
 <olteanv@...il.com>
Subject: [ANN] netdev call - Jun 18th

Hi!

The bi-weekly call is scheduled for tomorrow at 8:30 am (PT) / 
5:30 pm (~EU), at https://bbb.lwn.net/b/jak-wkr-seg-hjn

I have one agenda item which has been on my mind for a while.
We have set a policy to reject any new drivers supporting the
legacy SR-IOV ndos a couple of years back. The hope was that
this will spur investment in implementing more full featured
offloads like bridge or flower. My very subjective feeling is
that the policy has not had that effect. I wonder whether we
should consider allowing the basics (MAC, VLAN, link state,
spoof check) again. Obviously absolutely no extensions to the
APIs allowed.

Please join the call or share here if you have on opinion in
either direction. Especially if you know of people actually
working on an upstream/open solutions to this problem because
of the current policy.

Please feel free to send other agenda items for the call.

In terms of review rotation - it's an nVidia week.