From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Minutes of Technical Board meeting 24-January-2024
Date: Mon, 29 Jan 2024 11:03:27 +0000 [thread overview]
Message-ID: <ac567bd8-32a8-409b-8dd0-85212a119e4c@redhat.com> (raw)
Members Attending
-----------------
Aaron Conole
Bruce Richardson
Hemant Agrawal
Honappa Nagarahalli
Jerin Jacob
Kevin Traynor (Chair)
Konstantin Ananyev
Maxime Coquelin
Morten Brorup
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 2024-Feb-07 @ 3pm UTC, and will
be chaired by Konstantin.
Agenda Items
============
Arg parsing (Bruce)
-------------------
- 3 series proposed as per last TB minutes
http://inbox.dpdk.org/dev/DBAPR08MB581405E7CF23732B8941B10C98732@DBAPR08MB5814.eurprd08.prod.outlook.com
- Discussion about these series and if merging it contradicts with
longer term function based initialization
- There is still a need to handle arguments for the foreseeable future
- Consensus for adding helpers to argparse lib that eal will depend on
- Drivers may use an extension of argparse library in time
- Call for patch reviews
3 year LTS maintenance? [Kevin]
-------------------------------
- Current documented policy is for 2 years
- 19.11/20.11 LTS were maintained for 3 year and it went smoothly
- Proposal is to formally document 3 year LTS maintenance
- http://inbox.dpdk.org/dev/20240117162419.223820-1-ktraynor@redhat.com
- Needs ack from LTS maintainers and companies involved in validation
Application logging [Thomas]
----------------------------
- Should applications use rte_logs or printf ?
- rte_log is useful because it can be enabled/disabled
- interactive items like testpmd stats are better suited to printf
- driver specific directories should use rte_log
gov/tech board meeting items [All]
----------------------------------
- Thomas is starting investigation about DPDK with AI
- Discussed possibility of cloud companies publishing DPDK capability
and performance reports on dpdk website
- Some may prefer to publish on their own website
- If anyone has contacts or can help coordinate please reach out to Nathan
reply other threads:[~2024-01-29 11:03 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=ac567bd8-32a8-409b-8dd0-85212a119e4c@redhat.com \
--to=ktraynor@redhat.com \
--cc=dev@dpdk.org \
--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 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).