From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Cc: <techboard@dpdk.org>, <nsouthern@linuxfoundation.org>,
<probb@iol.unh.edu>
Subject: Minutes of techboard meeting, 2025-10-01
Date: Fri, 3 Oct 2025 10:17:37 +0100 [thread overview]
Message-ID: <aN-Use5rigF3tQc9@bricha3-mobl1.ger.corp.intel.com> (raw)
TB Members Attending: 7/11
--------------------------
- Bruce
- Thomas
- Kevin
- Konstantin
- Morten
- Jerin
- Maxime
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 October 15
Agenda
------
* LTS Maintainers,
- Project is currently short of LTS Maintainers.
- Enquiries are ongoing to find additional maintainers.
- Volunteers are welcome
- Mentoring and support from existing maintainers is available for new maintainers
* Use of FAST_FREE and multi-buffer/scattered mbuf flags
- The flags for enabling fast-free and supporting multi-mbuf packets are
now documented incompatible
- Previously they were not defined as incompatible, but that seems to
have been assumed for some usages.
- Techboard discussed how best to resolve this incompatibility with
regards to:
- ensuring correctness
- avoiding major churn to DPDK code
- avoiding churn to end-user code
- Options discussed:
1 change definition back to not have the settings incompatible: this
necessitates checking drivers for correctness
2 keep as explicitly incompatible and report error if both specified:
this could break end-user apps, and requires changes to example apps
3 drop the fast-free flag if multi-segment mbufs are also specified:
"hides" the issue, but probably minimises changes. Would need to
decide whether the dropping of flag done in drivers vs ethdev level.
Pros and cons to both options. Needs clear documenting.
- No firm decision reached, will discuss more over email.
Recurring item list Discussion
------------------------------
TB reviewed our standard list of recurring items for updates.
* Examples to remove:
- it was noted that work is being done on DCB functionality, and
separating it from VMDQ.
- follow up with patch author (as presumed knowledgable in this area) as
to whether we need to keep both vmdq and vmdq+dcb sample apps.
* Doc Maintenance:
- Project had employed a technical writer to help cleanup docs, but this
contract has now finished
- Most output patches from the contract have been merged but there is at
least one set that needs futher update
- Discussed use of AI for documentation updates
- for mechanical updates AI may be of help
- skepticism of usefulness beyond that
* Community Lab:
- Patrick provided a short update on lab work:
- DTS Development ongoing
- Team at UNH has produced some new introductory videos on setting up
and using DTS.
- Process has just started on planning for lab priorities for 2026, in
order to have that in place for end-of-year.
next reply other threads:[~2025-10-03 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 9:17 Bruce Richardson [this message]
2025-10-06 14:40 ` Minutes of techboard meeting, 2025-10-01 Morten Brørup
2025-10-07 7:58 ` Stephen Hemminger
2025-10-08 12:36 ` Use of TX offload flags MBUF_FAST_FREE and MULTI_SEGS Morten Brørup
2025-10-06 14:51 ` Morten Brørup
2025-10-06 14:59 ` Ivan Malov
2025-10-29 20:32 ` 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=aN-Use5rigF3tQc9@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nsouthern@linuxfoundation.org \
--cc=probb@iol.unh.edu \
--cc=techboard@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 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.