From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2023-August -9
Date: Tue, 22 Aug 2023 10:23:15 +0000 [thread overview]
Message-ID: <BY3PR18MB4785417C5EE9993FAE34D0CBC81FA@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
Minutes of Technical Board Meeting, 2023-August -9
Members Attending
-----------------
-Aaron
-Bruce
-Hemant
-Honnappa
-Jerin (Chair)
-Konstantin
-Stephen
-Thomas
-Tyler
-Morten
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- August -23 @3pm UTC, and will be chaired by Honnappa
Dublin DPDK submit
------------------
Collected various topics to be discussed in tech-board meeting on 11th September 2023 evening.
1) General tech-board discussion on the
- Process of adding/removing tech-board members
- Expected size of tech-board Do we want more people? Less? Grow the TB or expand it?
- Specific individuals who wish to join or leave the TB within the next year?
- Efficient ways to split the work up etc.
2) Discussion led by Aaron on the possible automation of patches in the future - pros? Cons ? Worth implementing? Best process if this route is pursued.
3) Internal review process: how to accelerate and/or improve this - more comments, addressing/responding to these comments, etc.
4) Improvements in use of lab resources by maintainers and committers - additional branches, etc.
DPDK C11 atomics integration challenges
----------------------------------------
1) Discussed various issues with C11 atomics integration like
- rte_ring performance issue C11 atomics
- ABI compatibility issues in public header due to atomics size differences
- c++23 clang distribution issues
- In general agreed to have DPDK specific prefix for better integration of atomics primitives by providing room to
accommodate compiler specific differences, Tyler Retzlaff will send a RFC for the same.
RFC is at https://patches.dpdk.org/project/dpdk/list/?series=29255
reply other threads:[~2023-08-22 10:23 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=BY3PR18MB4785417C5EE9993FAE34D0CBC81FA@BY3PR18MB4785.namprd18.prod.outlook.com \
--to=jerinj@marvell.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).