From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
Nathan Southern <nsouthern@linuxfoundation.org>
Subject: Minutes of Technical Board Meeting, 2023-March-8
Date: Fri, 17 Mar 2023 04:51:30 +0000 [thread overview]
Message-ID: <BY3PR18MB4785111EB04ED23CB0CB0107C8BD9@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2023-March-8
Members Attending
-----------------
-Aaron
-Bruce
-Hemant
-Honnappa
-Jerin (Chair)
-Kevin
-Konstantin
-Maxime
-Stephen
-Thomas
NOTE: The technical board meetings every second Wednesday at https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2023-March-23 @3pm UTC, and will be chaired by Kevin
1) Nathan provided an update on the hiring of a Technical Writer. The hiring interviews are currently in progress.
2) Multiple MAC address support and API behavior were discussed.
- Various approaches were considered, such as "adding separate functions for multi MAC address" or "changing the existing function to support multiple MAC addresses for better API".
- The TB has not concluded on a specific approach and has invited Ferruh Yigit for the next TB meeting to get more data points on this discussion.
3) Testpmd update for VXLAN packet generation
- TB recommends using existing traffic generators like DPDK packet-gen for this purpose.
- TB decided to not enhance testpmd for this specific case.
- However, if the existing traffic generators are not suitable and if the author can provide technical and managerial justification (such as a lack of maintenance, too many bugs, or excessive complexity), then the author may propose an in-tree example application for packet generation.
4) Thomas raised concern about the lack of documentation of usage and appropriate selection of the logs, telemetry, and trace in various scenarios. Requested Bruce to send a documentation update patch for the same.
5) There was a discussion about pending DTS patches in the DPDK mailing list. Thomas is planning to merge them in RC3.
reply other threads:[~2023-03-17 4:51 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=BY3PR18MB4785111EB04ED23CB0CB0107C8BD9@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=nsouthern@linuxfoundation.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).