From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board meeting 18-October-23
Date: Fri, 20 Oct 2023 17:21:27 +0100 [thread overview]
Message-ID: <0520f6a2-d98f-260d-8998-9bff8b8797e8@redhat.com> (raw)
Members Attending
-----------------
Aaron Conole
Bruce Richardson
Hemant Agrawal
Honappa Nagarahalli
Jerin Jacob
Kevin Traynor (Chair)
Konstantin Ananyev
Maxime Coquelin
Stephen Hemminger
Thomas Monjalon
NOTE: The technical board meetings are on every second Wednesday at 3 pm
UTC.
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
Next meeting will be on Wednesday 2023-Nov-02 @ 3pm UTC, and will
be chaired by Aaron.
Agenda Items
============
Experimental API promotion (David)
----------------------------------
- Some experimental API being called from inline helper triggering a
warning in applications not compile with experimental API (e.g. OVS)
- Patch submitted to promote those API to stable early
(https://patchwork.dpdk.org/project/dpdk/patch/20231018091123.1594324-1-david.marchand@redhat.com/)
- Simple signature, not likely to need to be changed
- Promotion to stable API approved
- Some increased documentation on endianness needed
- Checks can be added to CI to prevent a re-occurrence as a later step
Increase max lcores for AMD EPYC CPUs (Sivaprasad)
--------------------------------------------------
- Patch to increase max core count for native AMD EPYC builds
(http://inbox.dpdk.org/dev/20230925151027.558546-1-sivaprasad.tummala@amd.com)
- There is some asks for more than 128 worker cores
- Discussion about generally increasing the default max core count and
trade-offs with memory consumption but this is longer term issue
- Acceptance for the direction of this patch in the short term
- Details of whether it should be for EPYC only or x86 to be figured out
on mailing list
Conclusion of joint meeting yesterday between two boards (Nathan)
-----------------------------------------------------------------
- Exploring option of adding developer in UNH for DTS
- Ben presented some ideas around developer focused campaigns for 2024
-- reports/code challenges/swag as well as continuing user stories/blogs
- Discussion on exploring how DPDK can help with Cloud/Security/AI
Website meeting minutes/invite (Kevin/Thomas)
---------------------------------------------
- Any TB minutes available but missing from list Thomas sent, please let
him know
- Thomas will send patch with updated TB minutes and new meeting invite
AOB
---
- UNH lab will give update on 2023 progress in next TB meeting
-- Discussion may start on 2024 priorities
-- Aaron will poll for 2024 items soon
- Ferruh would like more reviews on bonding patches that have specific
APIs and change ethdev structs
(https://patchwork.dpdk.org/project/dpdk/list/?series=29900&state=*)
- Some maintainers have changed priorities and have less time now
-- There is a need for more maintainers to help with patch review/merging
reply other threads:[~2023-10-20 16:21 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=0520f6a2-d98f-260d-8998-9bff8b8797e8@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).