From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes of July 18
Date: Mon, 06 Aug 2018 13:23:52 +0200 [thread overview]
Message-ID: <15035621.e5pW3VzH88@xps> (raw)
Meeting notes for the DPDK technical board meeting held on 2018-07-18
Attendees:
- Bruce Richardson
- Ferruh Yigit
- Jerin Jacob
- Konstantin Ananyev
- Olivier Matz
- Thomas Monjalon
1/ Power management patches
- examples/vm_power: 100% Busy Polling
decision: to RC2
- lib/librte_power: traffic pattern aware power control
decision: to 18.11
2/ Maintenance of examples
The examples directory can be used as a staging area for some features.
And the techboard must do a periodically audit of this directory.
The actions to take can be:
- move code into libraries
- merge examples
- drop example
3/ Recurring agenda items
Some recurring items will be added to the techboard agenda:
- examples audit
- meson migration
- SPDX compliance
4/ Required talks for Dublin event
- community process improvements
- memory rework
- do less by default
More details about the last one:
The application must own the configuration (including for threads),
while EAL provide some good defaults, some parsing helpers and a fine-grain API.
reply other threads:[~2018-08-06 11: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=15035621.e5pW3VzH88@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).