From: Jerin Jacob <jerinj@marvell.com>
To: dev <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2025-May-28
Date: Fri, 13 Jun 2025 08:29:42 +0000 [thread overview]
Message-ID: <BY3PR18MB47853E2B0132CF340294A2E2C877A@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2025-May-28
Members Attending
-----------------
-Aaron
-Bruce
-Hemant
-Jerin
-Kevin (Next Chair)
-Konstantin
-Maxime
-Morten
-Stephen
-Thomas
NOTE: The technical board meetings every second Wednesday at
https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efebat 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2025- June - 11th @3pm UTC, and will be chaired by Kevin
1) License Exception for getline() Function in Windows EAL
a) Stephen to communicate the license exception request to the Governing Board.
b) The Technical Board agreed to grant an exception for the use of getline() in Windows EAL.
c) The Governing Board subsequently approved the exception in a later meeting.
2) ABI Stability - Key Considerations
The board had a detailed discussion on ABI stability. No final decisions were made, and the topic will continue to be explored. Key discussion points included:
a) Proposal to extend the ABI compatibility window from 1 year to 2 years.
b) Evaluated the feasibility of making asymmetric crypto device functions non-inline.
c) Encouraged use of initialization functions for public structures, acknowledging that full coverage may not be achievable.
d) Concerns from consumers (e.g., OVS) regarding delays caused by ABI change restrictions; suggestion to consider multiple LTS streams as a potential solution.
e) Observed that product owners prefer LTS, regardless of ABI/API changes.
f) Suggested that ABI changes be limited to non-LTS versions.
g) Agreed to continue discussions at the upcoming U.S. Summit and via the DPDK mailing list on above suggestion.
h) Topic to remain on the agenda for the next Technical Board meeting.
3) MACB Driver Enablement
a) Scheduled for discussion in the next Technical Board meeting
reply other threads:[~2025-06-13 8:29 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=BY3PR18MB47853E2B0132CF340294A2E2C877A@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.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).