From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: [dpdk-dev] DPDK techboard minutes for Apr 22nd 2020
Date: Thu, 23 Apr 2020 19:46:13 +0000 [thread overview]
Message-ID: <DBBPR08MB4646FF866436A6E9F26936CC98D30@DBBPR08MB4646.eurprd08.prod.outlook.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2020-04-22
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Honnappa Nagarahalli (Chair)
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
NOTE: The technical board meetings every second Wednesday on IRC channel #dpdk-board, at 3pm UTC. Meetings are public and DPDK community members are welcome to attend.
NOTE: Next meeting will be on Wednesday 2020-05-06 @3pm UTC, and will be chaired by Jerin
1) Merging app/test-flow-perf in 20.05
- This application will be kept separate from testpmd
- It is approved to be merged in 20.05
2) Timeline to stop using rte_atomicNN_xx, rte_smp_*mb APIs (other barrier APIs, rte_*mb, rte_cio_*mb, rte_io_*mb, are allowed to be used)
- The formal deprecation of these APIs, which affects the DPDK applications, is postponed to a later point
- It was agreed to stop accepting new code with the above APIs after 20.05 release
(subject to the availability of the patch for wrappers for C11 atomic built-ins) - AI, Honnappa
- Add a note in the release notes to indicate the same - AI, Honnappa
3) Wrappers for C11 atomic built-ins will not be available for 20.05. Patches using C11 atomic built-ins will be accepted for 20.05
(as there is already lot of code with C11 atomic built-ins)
4) Need volunteers for maintaining C11 code
- This role is to support the maintainers with questions, help debug issues
- It would be good to have one maintainer from each supported architecture, volunteers are needed
- Honnappa is the maintainer from Arm
5) Ask Windows team to build and test with C11 code enabled in CI (for ex: rte_ring) - AI, Thomas
6) Multi-function chaining APIs
- A conclusion could not be reached. The discussion/voting is still ongoing. I will post the update once the decision is done.
Thank you,
Honnappa
next reply other threads:[~2020-04-23 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 19:46 Honnappa Nagarahalli [this message]
2020-05-05 23:48 ` Honnappa Nagarahalli
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=DBBPR08MB4646FF866436A6E9F26936CC98D30@DBBPR08MB4646.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--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).