From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Cc: Shannon Nelson <shannon.nelson@amd.com>,
Vladimir Oltean <olteanv@gmail.com>
Subject: [ANN] netdev call - Jun 18th
Date: Mon, 17 Jun 2024 08:39:55 -0700 [thread overview]
Message-ID: <20240617083955.1039b2e3@kernel.org> (raw)
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.
reply other threads:[~2024-06-17 15:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240617083955.1039b2e3@kernel.org \
--to=kuba@kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=shannon.nelson@amd.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).