From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK techboard minutes for 19th of December
Date: Thu, 17 Jan 2019 09:49:24 -0800 [thread overview]
Message-ID: <20190117094924.1fa8148b@hermes.lan> (raw)
Meeting notes for the DPDK technical board meeting held on 2019-12-19
Sorry for the belated minutes, but the puppy hair killed my desktop ;-)
Attendees: 6/9
- Thomas Monjalon
- Bruce Richardson
- Ferruh Yigit
- Maxime Coquelin
- Olivier Matz
- Stephen Hemminger
KNI
The existing KNI device is getting trimmed for 19.02.
Consensus this is good, and hope is that KNI can get more work
to improve performance (currently virtio is faster).
Build System
Still not enough automated build and testing is done on DPDK patches.
Investigating getting Open Build Service (SUSE) as continuous build service
to check all patches on all architectures. Luca will do more
investigation.
Mentoring
Testing and build systems are a good way to get new people involved.
Shemminger will look into applying for Google Summer of Code
mentoring.
Test Lab
Discussion of current test lab. Current testing is limited to single
core and only a performance test. Consensus that more investment and
time is needed to get results from the lab. A wider scope is needed.
What about testing stable branches as well?
Process discussion
Ongoing Discussion about gerrit etc. versus current process.
Everyone agrees that current dev mailing list is overloaded to the
point that only a few people read all of it. Ideas included splitting
the mailing list along functional lines (crypto, compress, ipsec, ...)
but concern that then overlapping patches would not get reviewed.
General conclusion that mail is not scaling well, some alternative
mail clients and tools discussed but no actions taken.
next reply other threads:[~2019-01-17 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 17:49 Stephen Hemminger [this message]
2019-01-17 18:28 ` Luca Boccassi
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=20190117094924.1fa8148b@hermes.lan \
--to=stephen@networkplumber.org \
--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).