DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: "Ma, LihongX" <lihongx.ma@intel.com>
Cc: Brandon Lo <blo@iol.unh.edu>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	 David Marchand <david.marchand@redhat.com>,
	"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
	 Thomas Monjalon <thomas@monjalon.net>,
	"ci@dpdk.org" <ci@dpdk.org>, "Tu, Lijuan" <lijuan.tu@intel.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>,
	"Zhang, XuemingX" <xuemingx.zhang@intel.com>,
	 "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: [dpdk-ci] upgrade dts to use meson build test intel ci performance
Date: Fri, 18 Sep 2020 08:59:06 -0400	[thread overview]
Message-ID: <CAOE1vsOw-RvPeCVYAzrTNvg4RkBUZV6b7+y_t4PF=4JSdEbKdw@mail.gmail.com> (raw)
In-Reply-To: <BN8PR11MB37158C93134720365E183F6B9E3F0@BN8PR11MB3715.namprd11.prod.outlook.com>

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

Hello Ma,lihong,

I believe Brandon already updated the version of DTS on the Intel and
Broadcom machines and those are in production testing for the CI. The Inel
10G is still offline, while we're integrating some of the functional
testing on that platform, before it expands out to other testing.

Cheers,
Lincoln

On Fri, Sep 18, 2020 at 4:20 AM Ma, LihongX <lihongx.ma@intel.com> wrote:

> Hi, Brandon
>
>
>
> As dpdk discontinued make support for compiling,  a dts upgrade is needed
> for intel ci performance on NNT and FVL env.
>
>
>
> What the time is proper for me to upgrade and debug them ?
>
>
>
>
>
> Regards,
>
> Ma,lihong
>
>
>


-- 
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 3137 bytes --]

  reply	other threads:[~2020-09-18 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  8:19 Ma, LihongX
2020-09-18 12:59 ` Lincoln Lavoie [this message]
2020-09-22  2:52   ` Ma, LihongX

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='CAOE1vsOw-RvPeCVYAzrTNvg4RkBUZV6b7+y_t4PF=4JSdEbKdw@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dpdklab@iol.unh.edu \
    --cc=lihongx.ma@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@intel.com \
    --cc=xuemingx.zhang@intel.com \
    --cc=zhaoyan.chen@intel.com \
    /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).