From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: Minutes of DPDK Technical Board Meeting, 2026-07-08
Date: Thu, 20 Aug 2026 11:52:17 +0200 [thread overview]
Message-ID: <BSRP-D5wSaeJaTYH_K8E1A@monjalon.net> (raw)
Members Attending: 7/10
- Aaron Conole
- Bruce Richardson
- Hemant Agrawal
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Thomas Monjalon (Chair)
NOTE: The Technical Board meetings take place every second Wednesday at 3 pm UTC
on https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efeb
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
The next meeting will happen on July 22 and will be chaired by Morten Brørup.
1/ EAL initialization
Bruce is working on patches published as RFC in April:
https://patches.dpdk.org/project/dpdk/cover/20260429165845.2136843-1-bruce.richardson@intel.com/
The patches are improving how configuration is stored in EAL.
It may help to better split EAL.
And the goal is to initialize EAL without argc/argv.
There are many parameters and we must keep compatibility with the existing API.
It is a call for review and give high level feedbacks
like is it worth refactoring? how the interface should look like?
2/ UNH lab CI coverage
Lincoln asked what to present in coverage reports
regarding specific NIC drivers:
https://mails.dpdk.org/archives/dev/2026-June/339545.html
Considering the limited number of NICs in the lab at the moment,
it's probably better to start small and focus on the libraries coverage.
If some NICs help to cover more library features, we could combine them.
reply other threads:[~2026-08-20 9:52 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=BSRP-D5wSaeJaTYH_K8E1A@monjalon.net \
--to=thomas@monjalon.net \
--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