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>
Subject: [dpdk-ci] Minutes of DPDK Lab Meeting, November 28th
Date: Fri, 1 Dec 2017 09:37:48 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4A7A0FA@IRSMSX108.ger.corp.intel.com> (raw)

Here are some brief minutes of our call on Tuesday.

Database Schema:
- Patrick has proposed an initial schema.
- Discussed debugging and log information. If a developer submits a patch, the performance lab results show that it negatively impacts performance on a hardware platform, but the developer does not have access to that type of platform, how do they debug the issue?
- Agreed that the immediate priority is to get tests running, and that debug/log info is a lower priority.
- Vendors contributing hardware should be able to set the log level for tests on their platform. Typically this would be set to the lowest level in order to show the best performance. Ideally this should be consistent across vendors.
- Logs should not be available by default, but it should be possible for vendors to over-ride this and make logs available if they choose to do so.
- Patrick will look into how log output can be stored and linked to from the schema. He'll also address other comments from Thomas and Gema.

DTS & TRex:
- Qian: Can you provide a target date for when we expect TRex support to be added to DTS?
- Mellanox plan is to work on DTS in the second half of December, but this depends on TRex support.
- NXP have DTS and Pktgen working. Haven't tried TRex yet.
- Intel hardware should be ready for shipping soon (no exact date yet). We're working on setup instructions for UNH. Mellanox are targeting end of Dec. NXP are targeting Jan.

Next Meeting:
- Tuesday Dec 12th. That will be our last meeting this year.

                 reply	other threads:[~2017-12-01  9:37 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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4A7A0FA@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=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).