From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2023-April-19
Date: Tue, 23 May 2023 09:39:30 +0200 [thread overview]
Message-ID: <6b25a7d4-12fe-9256-a69f-5d611b7e23c5@redhat.com> (raw)
Minutes of Technical Board Meeting, 2023-April-19
Members Attending
-----------------
-Aaron
-Bruce
-Hemant
-Honnappa
-Jerin
-Kevin
-Konstantin
-Maxime (Chair)
-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-May-3 @3pm UTC, and will be
chaired by Stephen.
1) Welcoming Dave Young, our new technical writer
- Dave will start his new role on June 12th.
- He lives in Georgia (US) and has a Master degree in Professional
writing.
2) Direct-rearm/Buffer-recycle patch set discussions
- Honnappa and Ferruh put together a slide deck presenting the feature
- Goal of the series is to provide a new mechanism to free the buffers
directly into the Tx software ring, an so avoid free/alloc from the
lcore cache.
- Gains up to 17% with l3fwd on Ampere Altra
- No major objections from the Technical board, but suggestion to
provide a new forward mode to testpmd to exercise the new API, and also
to add a namespace to the API names to highlight they belong to the same
feature.
3) Technical board updates for the Governing board meeting
- Kevin asked if Techboard members had updates to share at theGoverning
board meeting.
- He will send a list of updates to the Techboard mailing list.
4) Marketing group updates
- Thomas invites the Techboard to join the Marketing group meetings.
reply other threads:[~2023-05-23 7:39 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=6b25a7d4-12fe-9256-a69f-5d611b7e23c5@redhat.com \
--to=maxime.coquelin@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).