From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2021-01-27
Date: Thu, 28 Jan 2021 12:09:23 +0000 [thread overview]
Message-ID: <eb9bcc03d91c4a9a89f606fd83707e08@intel.com> (raw)
NOTE: The Technical Board meetings take place every second Wednesday
on https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
NOTE: Next meeting will be on Wednesday 2021-02-10 @3pm UTC,
and will be chaired by Ferruh
Meeting Minutes
================
Maintainership
* New LTS maintainer approved by TB
* Christian Erhardt will take on responsibility as LTS maintainer for DPDK
* Christian would take on 19.11, Luca to take 20.11
DPDK Asia Conference Event
* AR: Techboard members - review spreadsheet by end of this week
* AR: Techboard members - Complete doodle poll for meeting ASAP
Backport Performance Optimizations
* Ask on mailing list to have performance optimization patches backported into LTS release
* Concerns expressed about this:
- New code is viewed as potentially unstable
- New code for opt is like introducing a new feature - perhaps worse as potentially breaking something working, rather than adding on.
* Other considerations mentioned (some already called out on mailing list)
- Performance regressions should be considered separately.
- Validation support - need submitter to provide validation tests
- Potentially different rules for latest LTS vs other LTS?
- Effort involved for LTS maintainers?
- If any queue for patches, bug fixes must take priority.
* **Consensus Reached**
1. no optimization backports at this point. Fixes for performance regressions will be considered on a case by case basis.
2. AR: Kevin and Luca to document some policies for discussion.
List of supported OS's and compilers
* Previously agreed just to advertise what is tested
Lab
* Meetings ongoing to define objectives for lab
* On-going discussions in governing board re. coverage etc.
DPDK Build Configuration
* First draft of current design doc sent by Bruce to TB
* AR: Ask for TB to review
KNI
* Deprecation moved to recurring items
Status of Trex:
* Has forked copy of DPDK
- Some extra DPDK patches not upstreamed
- Has additional PMD
- Uses old build system
* Trex is used in lab which causes problems:
- New HW/drivers are not supported in forked copy
Further discussion needed on the topic of traffic generators for lab use.
reply other threads:[~2021-01-28 12:09 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=eb9bcc03d91c4a9a89f606fd83707e08@intel.com \
--to=bruce.richardson@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).