From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Subject: Re: [ANN] netdev call - Jan 16th
Date: Wed, 17 Jan 2024 14:26:23 -0800 [thread overview]
Message-ID: <20240117142623.1cce7adf@kernel.org> (raw)
In-Reply-To: <20240115175440.09839b84@kernel.org>
On Mon, 15 Jan 2024 17:54:40 -0800 Jakub Kicinski wrote:
> The bi-weekly netdev call at https://bbb.lwn.net/b/jak-wkr-seg-hjn
> is scheduled tomorrow at 8:30 am (PT) / 5:30 pm (~EU).
>
> There's a minor CI update. Please suggest other topics.
Sorry about the delay in sending minutes, here they are:
* BQL (Dave Taht)
* Embedded drivers missing BQL
* Complain to the driver maintainers
* Driver review time is best to request basic features like BQL
* Some of the problems are in the vendor downstream drivers
* Are vendors running flent and other latency tests?
* Jesse: yes, although they struggle at DC speeds
* Multi-queue BQL
* Not much interest among attendees
* Andrew: try to keep it in the core, fewer driver changes the better
* CI
* Most of the networking selftests are now run on pending patches
* https://netdev.bots.linux.dev/status.html
* Not reporting back to patchwork, yet, because there’s a bunch of
pre-existing failures
* Paolo: we should extend the tests with mptcp tests
* DSA tests may also be useful - Andrew to investigate if they can run in SW
* We’re looking to integrate with other people running tests themselves
Unrelated to the call, but we have also posted a "2023 netdev
retrospective": https://people.kernel.org/kuba/netdev-in-2023
prev parent reply other threads:[~2024-01-17 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 1:54 [ANN] netdev call - Jan 16th Jakub Kicinski
2024-01-16 15:19 ` Andy Gospodarek
2024-01-16 15:29 ` John Fastabend
2024-01-16 16:04 ` Andy Gospodarek
2024-01-16 16:10 ` Andrew Lunn
2024-01-16 16:12 ` Andy Gospodarek
2024-01-16 18:43 ` Florian Fainelli
2024-01-17 22:26 ` Jakub Kicinski [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=20240117142623.1cce7adf@kernel.org \
--to=kuba@kernel.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.