DPDK CI discussions
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Cc: 'Trishan de Lanerolle' <tdelanerolle@linuxfoundation.org>,
	"'Bob Noseworthy'" <ren@iol.unh.edu>,
	'Shreyansh Jain' <shreyansh.jain@nxp.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	'Shepard Siegel' <shepard.siegel@atomicrules.com>,
	'Thomas Monjalon' <thomas@monjalon.net>,
	'Erez Scop' <erezsc@mellanox.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	Patrick MacArthur <patrick@patrickmacarthur.net>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, August 22nd
Date: Tue, 22 Aug 2017 21:07:16 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA404774D@IRSMSX101.ger.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2022 bytes --]

Distribution list:
- We agreed to use the ci@dpdk.org mailing list for any future discussion on the lab, so I've used it for these minutes. I've copied those who were on the previous distribution for the minutes, in case anybody has not yet subscribed to ci@dpdk.org. If you haven't subscribed yet, you can do so at: http://dpdk.org/ml.

Lab Contract:
- The draft contract, with changes based on the LF review, is attached. Others should review this and return comments to Bob (ren@iol.unh.edu) by Friday 
September 1st. We'll discuss any significant issues at our next meeting on September 5th.
- The UNH-IOL Usage Agreement is also attached, and is also available at: https://www.iol.unh.edu/sites/default/files/charters/unh-iol-usage-agreement.pdf. People may want to review this as well.

Hardware:
- NXP and Intel hardware is in procurement. Mellanox hardware is ready but needs internal approval before shipping to UNH.

CI:
- The script Mellanox have been working on to identify the target repository for a patch set is being reviewed internally and should be sent to the mailing list soon.
- Fangfang has sent a patch that includes a reference doc and some other scripts. Thomas will review this.

Test Results:
- Discussed whether we always need to provide absolute numbers for test results, or if delta values can be provided in some cases. Providing delta values may be useful for new hardware or new tests that have not yet been fully tuned, where vendors do not want to make absolute numbers public.
- Agreed that we should be able to decide per vendor and per test case whether absolute or delta numbers should be provided. This should be configured as part of the test script, so that the result is either the absolute performance number or a delta comparing this to a previous reference value.

Future meetings:
- Agreed to continue these meetings on a bi-weekly basis for now. If anybody else on this mailing list wants to join, let me know and I'll forward the meeting details. 



[-- Attachment #2: DPDK_SOW_Draft_2017_08_08-mkd.docx --]
[-- Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Size: 53590 bytes --]

[-- Attachment #3: unh-iol-usage-agreement.pdf --]
[-- Type: application/pdf, Size: 216178 bytes --]

             reply	other threads:[~2017-08-22 21:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 21:07 O'Driscoll, Tim [this message]
2017-08-30 17:03 ` Trishan de Lanerolle
2017-08-30 17:10   ` Shepard Siegel
2017-09-05  9:49   ` Thomas Monjalon

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=26FA93C7ED1EAA44AB77D62FBE1D27BAA404774D@IRSMSX101.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=ci@dpdk.org \
    --cc=erezsc@mellanox.com \
    --cc=john.mcnamara@intel.com \
    --cc=patrick@patrickmacarthur.net \
    --cc=qian.q.xu@intel.com \
    --cc=ren@iol.unh.edu \
    --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).