From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of March 14
Date: Mon, 26 Mar 2018 14:34:36 +0200 [thread overview]
Message-ID: <1900887.c5JPCJMrX2@xps> (raw)
Meeting notes for the DPDK technical board meeting
held on 2018-03-14
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
- Yuanhan Liu
0/ Check action items from last meetings
- list of files and initial authors for SPDX compliance
Hemant will send the list soon.
- list of gaps in the new build system
Bruce has not documented them yet.
- old patches in patchwork
Thomas should work with patchwork community to get more tooling.
We must send comments in old patch threads and close some.
- backup maintainer guidelines
Some sub-trees (net, crypto, event) should find a backup.
- MAINTAINERS file for trees
Thomas will send a patch to sort trees at the beginning of the file.
1/ Stable releases roadmap:
http://dpdk.org/ml/archives/web/2018-March/000615.html
- stable maintainers
Kevin Traynor was approved as maintainer of the LTS branch 18.11.
- release schedule
It looks difficult to have an early first stable release.
The earlier can be after the next RC1 validation tests are passed.
Suggestions should be sent in the email thread.
2) Check progress of few changes:
- memory rework
This big change is under testing and still on track for 18.05.
- offload API
Patches are missing for some PMDs.
Update: there are commitments for all of them in 18.05.
The deprecation notice will be updated to remove only the old
driver interface in 18.05.
The application interface (API) should be removed in 18.08.
- uevent hotplug
Still a lot of opens to discuss but not enough interest in emails.
- devargs syntax
Gaetan sent some patches which must be reviewed quickly.
- CRC_STRIP offload
Default should be CRC stripping.
If a PMD lacks the capability, it can be emulated.
A new flag to keep the CRC must be introduced.
- minimal kernel requirement
Not discussed because of time out.
reply other threads:[~2018-03-26 12:34 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=1900887.c5JPCJMrX2@xps \
--to=thomas@monjalon.net \
--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).