From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2020-07-01
Date: Fri, 10 Jul 2020 17:23:07 +0200 [thread overview]
Message-ID: <20200710152307.GH5869@platinum> (raw)
Meeting notes for the DPDK technical board meeting held on 2020-07-01
Members Attending
-----------------
- Bruce
- Ferruh
- Hemant
- Honnappa
- Jerin
- Kevin
- Konstantin
- Olivier (chair)
- Stephen
- Thomas
The technical board meetings takes place every second Wednesday on IRC
channel #dpdk-board, at 3pm UTC. Meetings are public and DPDK community
members are welcome to attend.
Next meeting will be on Wednesday 2020-07-15 @3pm UTC, and will be
chaired by Stephen.
Providing driver-specific data-path APIs in DPDK
------------------------------------------------
Following this thread http://patchwork.dpdk.org/patch/71445.
The techboard voted that data-path driver-specific APIs relying on
hardware descriptors in DPDK are allowed.
Despite some risks (more work for maintenance, lack of consistency,
vendor locking, less focus on generic APIs), we think performance
improvement justifies it in this case.
Future similar changes will still require an approval from the techboard
if there is no consensus in mailing list.
Renaming default git branch names
---------------------------------
The 'master' branches in DPDK git repositories will be renamed right
after the 20.08 release. It will be announced in 20.08 deprecation
notice.
The name of the branch in the main repository will be 'main'.
The branch name for each -next repository is up the the tree maintainers.
reply other threads:[~2020-07-10 15: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=20200710152307.GH5869@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@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).