From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of March 28
Date: Tue, 10 Apr 2018 12:02:11 +0200 [thread overview]
Message-ID: <2281218.6GQzG2sPvV@xps> (raw)
Meeting notes for the DPDK technical board meeting
held on 2018-03-28 at 3pm UTC
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Thomas Monjalon
1/ Backup maintainers for some -next trees (net, crypto, event)
Approved:
- Harry Van Haaren as next-event tree backup maintainer.
- Akhil Goyal as next-crypto tree backup maintainer.
2/ Extension of dpdk-next-crypto scope
The libraries and drivers for bbdev and compressdev will be managed
in dpdk-next-crypto, without renaming the tree.
3/ NFF-Go hosting
The techboard representative (Jerin) will ask the Governing Board
to open the umbrella for hosting NFF-Go on dpdk.org.
Need to wait for final decision.
4/ Check progress of few changes:
- memory rework
Waiting to fix performance regression on NXP.
- offload API
Most of PMDs are patched or promised to be. Looks OK.
next reply other threads:[~2018-04-10 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 10:02 Thomas Monjalon [this message]
2018-04-11 11:53 ` [dpdk-dev] [dpdk-techboard] " Jerin Jacob
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=2281218.6GQzG2sPvV@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).