DPDK CI discussions
 help / color / mirror / Atom feed
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>,
	Ali Alnubani <alialnu@mellanox.com>,
	'May Chen' <May.Chen@huawei.com>,
	"Lodha, Nishant" <Nishant.Lodha@cavium.com>,
	"Zhang, Chun" <chun.zhang@intel.com>,
	"Morgan, Jack" <jack.morgan@intel.com>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, February 20th
Date: Wed, 21 Feb 2018 14:03:47 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4AD102E@IRSMSX108.ger.corp.intel.com> (raw)

Test Infrastructure:
- Discussed distribution for email reports. Agreed that the ideal solution is for reports to be sent as a reply to the original patch. Patrick thinks this is possible and will investigate.
- Discussed how to handle the requirement to provide relative performance data. This is required by some vendors when the platform has not been fully tuned. The same performance tests should be run, but instead of reporting absolute values only values relative to previous test runs would be reported. This would still allow performance degradations to be identified, but would avoid making absolute throughput numbers publicly available before a platform has been fully tuned. Patrick proposed that we still store absolute data in the database, and implement restrictions on what's reported in the REST API that's used to access the database. Shreyansh will investigate to see if this meets NXP requirements.

Hardware Availability:
- Intel hardware is being prepared for shipping and should be sent soon.
- Mellanox have resolved the DTS/TRex issues they were encountering, with help from Patrick. Equipment will be prepared for shipping next week.
- Basic setup of NXP hardware is complete. Work on DTS is still in progress, and issues are being addressed.
- Cavium have indicated that they intend to provide hardware to the lab. Nishant will be the Cavium rep for this.

Next Meeting:
- Tuesday March 6th.

                 reply	other threads:[~2018-02-21 14:03 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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4AD102E@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=George.Y.Zhao@huawei.com \
    --cc=Matt.Spencer@arm.com \
    --cc=May.Chen@huawei.com \
    --cc=Nishant.Lodha@cavium.com \
    --cc=Shishir.Mishra@spirent.com \
    --cc=alialnu@mellanox.com \
    --cc=chun.zhang@intel.com \
    --cc=ci@dpdk.org \
    --cc=erezsc@mellanox.com \
    --cc=gema.gomez-solano@linaro.org \
    --cc=georgii.tkachuk@intel.com \
    --cc=jack.morgan@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).