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, September 19th
Date: Fri, 22 Sep 2017 15:40:06 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BAA4070961@IRSMSX101.ger.corp.intel.com> (raw)
Here are some brief minutes of our call on Tuesday. Apologies for the delay in sending these out.
SOW & Usage Agreement:
- The only remaining issue is the concern over the wording relating to warranty that Erez raised. Trishan is following up with LF legal on this. Those of us in Dublin next week can discuss it in person there.
Userspace Presentation
- Qian sent on her draft slides for the CI/Lab session at the DPDK Summit Userspace event in Dublin next week.
Hardware Availability:
- Not many updates on this. For most vendors this is still in procurement. Hopefully we can begin shipping hardware to UNH in October. Until then, UNH are continuing prep work.
Infrastructure:
- NXP and Mellanox still plan to test DTS again when the TRex changes are available. Ideally, we'll all use the same framework and packet generator, but if this doesn't turn out to be feasible then these may need to be vendor-specific.
reply other threads:[~2017-09-22 15:40 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=26FA93C7ED1EAA44AB77D62FBE1D27BAA4070961@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).