From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of tech-board meeting 2018-01-31
Date: Sun, 11 Feb 2018 15:38:47 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725890571B9B@irsmsx105.ger.corp.intel.com> (raw)
Date: 31 Jan 2018
Attendees:
Bruce Richardson,
Ferruh Yigit,
Hemant Agrawal,
Jerin Jacob,
Konstantin Ananyev,
Olivier Matz,
Thomas Monjalon
Yuanhan Liu
Stephen Hemminger
Topic: Future plans for next-build tree and meson build system work in general across 18.05 and 18.08 releases.
* Some work for meson build system is still progress
* Bruce expects moderate number of patches for it 18.05 timeframe
* General conclusion:
- keep draft tree till 18.05 is out, after that all meson patches will go into the main tree
- Bruce to create a TODO list with all present gaps in the new build system should be provided
Topic: Port ownership patch series
* TB recommendation:
- Apply already ACKed patches.
- Don't apply tespmd patch (more work is required).
Topic: Disable all offloads by default in testpmd patch
* Concerns regarding disabling by default CRC_STIP and TX_FAST_FREE
* Conclusion:
- for 18.02 remove only VLAN offloads from current enabled by default set.
- for 18.05 see if CRC_STRIP offload can be removed at all
(expectation is that all PMDs can always run with CRC_STRIP on mode)
Topic: DPDK India summit
* Hemant and Jerin plan to give a presentation on it.
Topic: Need some action on source files in DPDK, which do not have any license and copyrights.
* Conclusion: publish a list with of the files and initial authors,
and give some time for people to claim files (with some reasonable proof).
Next Meeting:
* 2018-02-14 @ 3pm UTC
* Olivier to chair discussion as per alphabetical order
Konstantin
reply other threads:[~2018-02-11 15:38 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=2601191342CEEE43887BDE71AB97725890571B9B@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.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).