From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>
Cc: 'Bob Noseworthy' <ren@iol.unh.edu>,
'Erez Scop' <erezsc@mellanox.com>,
'Matt Spencer' <Matt.Spencer@arm.com>,
'George Zhao' <George.Y.Zhao@huawei.com>,
"'Mishra, Shishir'" <Shishir.Mishra@spirent.com>,
'Lixuming' <lixuming@huawei.com>,
"Tkachuk, Georgii" <georgii.tkachuk@intel.com>,
'Trishan de Lanerolle' <tdelanerolle@linuxfoundation.org>,
'Sean Campbell' <scampbel@qti.qualcomm.com>,
'May Chen' <May.Chen@huawei.com>,
"'Lodha, Nishant'" <Nishant.Lodha@cavium.com>,
"Zhang, Chun" <chun.zhang@intel.com>,
"'Malla, Malathi'" <Malathi.Malla@spirent.com>,
'khemendra kumar' <khemendra.kumar13@gmail.com>,
"Wang, Liang-min" <liang-min.wang@intel.com>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, August 28th
Date: Tue, 28 Aug 2018 20:47:56 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAB774ED58@IRSMSX107.ger.corp.intel.com> (raw)
Thomas highlighted some issues with sending these minutes to the ci@dpdk.org mailing list and copying a large number of people (basically the mailing list system doesn't seem to like it!). To avoid this, in future I'll send minutes only to ci@dpdk.org. If you haven't subscribed to that but want to continue to receive minutes, please sign up at: https://www.dpdk.org/contribute/#mailing-lists
Dashboard:
- Intel IXGBE (10Gbps) results still show occasional performance degradation when there shouldn't be any. Lijuan is unable to reproduce the problem in our lab.
- Lijuan has enabled the re-run option on the DTS so that it will run up to 3 times if there's a failure. To verify that this solves the problem, we need to re-run the tests on IXGBE for the last 1-2 weeks' patches. Jeremy will work on this.
- Zhaoyan will work with Jeremy to do some basic tests on the IXGBE system to verify that basic functionality is OK on the system.
- Larry and Zhaoyan are visiting UNH IOL on Thursday. If the problem hasn't been resolved by then they'll do further debug then.
- Ali has been reviewing the Mellanox results and everything looks stable. We'll need confirmation from Erez that Mellanox are OK to make the relative performance data public.
- NXP hardware has arrived in the lab and Shreyansh is working with Jeremy on setting it up.
- We hope to have relative performance data for Intel and Mellanox publically available before the Userspace event so that we can announce it then.
Userspace Event:
- Lijuan and Jeremy are presenting on CI and the open lab. They'll review slides to make sure they're giving a consistent message.
Contract:
- This has been extended to the end of 2018. Later this year we'll need to look at extending it again for 2019.
reply other threads:[~2018-08-28 20:48 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=26FA93C7ED1EAA44AB77D62FBE1D27BAB774ED58@IRSMSX107.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=George.Y.Zhao@huawei.com \
--cc=Malathi.Malla@spirent.com \
--cc=Matt.Spencer@arm.com \
--cc=May.Chen@huawei.com \
--cc=Nishant.Lodha@cavium.com \
--cc=Shishir.Mishra@spirent.com \
--cc=chun.zhang@intel.com \
--cc=ci@dpdk.org \
--cc=erezsc@mellanox.com \
--cc=georgii.tkachuk@intel.com \
--cc=khemendra.kumar13@gmail.com \
--cc=liang-min.wang@intel.com \
--cc=lixuming@huawei.com \
--cc=ren@iol.unh.edu \
--cc=scampbel@qti.qualcomm.com \
--cc=tdelanerolle@linuxfoundation.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).