From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] DPDK techboard minutes of October 24
Date: Sat, 10 Nov 2018 09:18:07 +0000 [thread overview]
Message-ID: <20181110091727.GA20155@jerin> (raw)
Meeting notes for the DPDK technical board meeting
held on 2018-10-24
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Hemant Agrawal
- Jerin Jacob
- Konstantin Ananyev
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
- Thomas Monjalon
0) DPDK acceptance policy on un-implemented API
- New APIs without implementation is not accepted.
- In order to accept a new API, At minimum
a) Need to provide an unit test case or example application
b) If the API is about HW abstraction, at least one driver
should be implemented. Preferably two.
c) If there are strong objections on ML about the need
for more than one driver for a specific API then
the technical board can make a decision.
- Konstantin volunteered to send existing un-implemented API
to the mailing list.
- The existing un-implemented APIs will be deprecated in v19.05.
- Deprecated un-implemented API will be removed in v19.08
1) jonathan.ribas@fraudbuster.mobi approached techboard to
include dpdk replay tool https://github.com/FraudBuster/dpdk-burst-replay
in dpdk.org
- TB to review the content and take the next steps
2) Next techboard meeting
- Konstantin Ananyev will chair it
next reply other threads:[~2018-11-10 9:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 9:18 Jerin Jacob [this message]
2018-11-12 9:34 ` Burakov, Anatoly
2018-11-12 11:24 ` [dpdk-dev] [dpdk-techboard] " Ananyev, Konstantin
2018-11-12 12:21 ` Richardson, Bruce
2018-11-12 12:36 ` Ananyev, Konstantin
2018-11-12 16:43 ` Stephen Hemminger
2018-11-12 16:55 ` Thomas Monjalon
2018-11-13 9:33 ` Burakov, Anatoly
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=20181110091727.GA20155@jerin \
--to=jerin.jacob@caviumnetworks.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).