From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "'ci@dpdk.org'" <ci@dpdk.org>
Cc: 'Bob Noseworthy' <ren@iol.unh.edu>,
"Mcnamara, John" <john.mcnamara@intel.com>,
'Shepard Siegel' <shepard.siegel@atomicrules.com>,
'Thomas Monjalon' <thomas@monjalon.net>,
'Erez Scop' <erezsc@mellanox.com>,
'Shreyansh Jain' <shreyansh.jain@nxp.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"'pmacarth@iol.unh.edu'" <pmacarth@iol.unh.edu>,
"'Matt Spencer'" <Matt.Spencer@arm.com>,
'Gema Gomez' <gema.gomez-solano@linaro.org>,
'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>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, January 23rd
Date: Tue, 23 Jan 2018 17:56:26 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4AAFB6E@IRSMSX108.ger.corp.intel.com> (raw)
Test Infrastructure:
- Patrick has a test setup in place which uses Jenkins to poll Patchwork for new patches, then runs DTS & Trex. Reporting has not been implemented yet.
- VPN infrastructure is setup and ready to provide vendor access when hardware is available.
DTS & TRex:
- TRex integration is available in the DTS next branch.
- Mellanox had an issue with the Tx offloads. Qian thinks that could be resolved by disabling offloads that are not supported on the Mellanox PMD.
- The firmware issue seen with TRex and the Intel 25G NIC is still being investigated but is not critical as our initial focus is on single core performance testing where this issue is not seen.
- Only single core performance test has been implemented for TRex so far, but it should be easy for Mellanox to add a max throughput test if they want to.
Hardware availability:
- For the Intel hardware, we need to resolve one problem with DTS running on the system before shipping. This is being investigated and is hopefully a minor configuration issue. Expect to ship hardware by the end of Jan.
- Mellanox are in a similar position and also expect to ship hardware by the end of the month.
- NXP are still working through the procurement process. It will take at least a month before they're ready to ship.
Schedule:
- Agreed that we'll target having live performance test results in the lab in Q2.
Next Meeting:
- Tuesday Feb 6th.
reply other threads:[~2018-01-23 17:56 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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4AAFB6E@IRSMSX108.ger.corp.intel.com \
--to=tim.odriscoll@intel.com \
--cc=George.Y.Zhao@huawei.com \
--cc=Matt.Spencer@arm.com \
--cc=Shishir.Mishra@spirent.com \
--cc=ci@dpdk.org \
--cc=erezsc@mellanox.com \
--cc=gema.gomez-solano@linaro.org \
--cc=georgii.tkachuk@intel.com \
--cc=john.mcnamara@intel.com \
--cc=lixuming@huawei.com \
--cc=pmacarth@iol.unh.edu \
--cc=qian.q.xu@intel.com \
--cc=ren@iol.unh.edu \
--cc=scampbel@qti.qualcomm.com \
--cc=shepard.siegel@atomicrules.com \
--cc=shreyansh.jain@nxp.com \
--cc=tdelanerolle@linuxfoundation.org \
--cc=thomas@monjalon.net \
/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).