From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2024-November-26
Date: Wed, 10 Dec 2025 15:01:50 +0000 [thread overview]
Message-ID: <d4dccf88-6813-4bbc-b75e-a8ea4240ce1b@redhat.com> (raw)
Minutes of Technical Board Meeting, 2024-November-26
Members Attending
*****************
- Aaron
- Hemant
- Kevin (Chair)
- Bruce
- Thomas
- Morten
- Stephen
- Konstantin
- Jerin
NOTE: The technical board meetings every second Wednesday at
https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2024- Dec - 10th @3pm UTC, and
will be chaired by Honnappa
# Lab SoW
- We got tech board quorum for voting for 2026 tasks.
- Patrick processed that into an SoW
- Governing board approved
- DTS development work being discussed
# Discussion of VLAN offload in PMD
- Discussion over patch for nbl driver that hard codes a return 0 for
vlan_offload_set callback
- https://inbox.dpdk.org/dev/20251124153545.7123c338@phoenix.local/
- vlan offload is done in software
- Issue is that existing OOT driver does this, so it would break apps vs
in-tree driver if it returned ENOSUP
- For current release, leave code as is
- For future release, consider to do some validation at ethdev level
# Driver Maintenance Discussion
- No updates
## Follow-up / Action Items
- Await update from Ajit regarding the new Broadcom maintainer
- Await Broadcom's plan for ongoing BNXT branch maintenance
- Discuss adding support-level flags to the maintainers file.
- Consider updates to documentation or policy for driver quality
expectations.
- Stephen to share proposal for marking drivers support-levels.
# AI
- Aaron ran some experiments in OVS using Claude code and Sonnet for
code review
- Results were better than CodeRabbit and Sourcery
- Aaron will select some DPDK patches to test with it
next reply other threads:[~2025-12-10 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 15:01 Kevin Traynor [this message]
2025-12-11 1:21 ` Stephen Hemminger
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=d4dccf88-6813-4bbc-b75e-a8ea4240ce1b@redhat.com \
--to=ktraynor@redhat.com \
--cc=dev@dpdk.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 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).