From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "techboard@dpdk.org" <techboard@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of October 10
Date: Tue, 23 Oct 2018 08:23:50 +0000 [thread overview]
Message-ID: <VI1PR0401MB25416EF6FDC9C8F0D1E5D65B89F50@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)
Meeting notes for the DPDK technical board meeting held on 2018-10-10
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
1) rte_ether.h conflict with standard headers
- At present, one cannot use netinet with DPDK
- Plan is to add rte_prefix to the current definitions in this header file.
- Olivier will send a deprecation notice for 18.11 timeframe.
- It will be fixed in 19.02 timeframe
2) 18.11 preparedness
- rte_flow needs backup maintainer. Ori's name was suggested.
- ipsec library will not make it for 18.11
- json - we don't want to write our own parser, distros are ok to support jansson.
- ARM community to check for dependency w.r.t cross compilation case.
3) US DPDK Summit
- it was suggested to do the CFP review on time and send the notifications asap.
4) Techboard rep in Governing Board.
- Konstantin will replace Jerin for next 4 month as TB rep in GB.
- Konstantin to confirm.
5) EAL Split: proposal to divide the EAL and move high level init in a separate library.
- it can be taken for 19.02. It will help libraries like telemetry.
6) Misc
- Stephen raised issue with constructors
- they are causing issues in some environments.
- an alternate can be doing it via EAL with some kind of registration mechanism.
- need a more solid alternate proposal before we pursue this change.
- it was suggested to remove experimental tags from some of the APIs before 18.11, specially the ones used by OVS.
7) Next techboard meeting
- It will be on October 24
- Jerin will chair it
reply other threads:[~2018-10-23 8: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=VI1PR0401MB25416EF6FDC9C8F0D1E5D65B89F50@VI1PR0401MB2541.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.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).