From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk1-f195.google.com (mail-qk1-f195.google.com [209.85.222.195]) by dpdk.org (Postfix) with ESMTP id D67F02B9E for ; Mon, 19 Nov 2018 18:52:45 +0100 (CET) Received: by mail-qk1-f195.google.com with SMTP id y16so50068553qki.7 for ; Mon, 19 Nov 2018 09:52:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=OuB14sbV04Ek3wxFE578WOJvC0FT+Fc+vGZuHdwLwOI=; b=KFjR9PIwDoYm/2VyQ2glbOo2j+dlHDAGeaNHYMyGZpd9CBsTzCd2a8ing+A37aGKdj 8WEMj98R0o5LBovPlbdPCSv14gv6nQaVaRqHxOj6JbEU59g2jZAVkXqnPeaNkogGUhy2 xOIl3BCOiNYmRVcO7ZshP/5YdsbMSS3IevenM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=OuB14sbV04Ek3wxFE578WOJvC0FT+Fc+vGZuHdwLwOI=; b=k0fxTDUdy34DHUJoYjrWG1TdKcVIu/kk/I9rV/Zs0vRJgOhRNDi6Czd8kqGL4UjUL5 X7tRkZBzDWvvO79w2k7UVfioqYXIHtVJi5ap04qCyTh4F2ljYBgQxw6ZbaRV+XGsF3SW PnzHlew+gkQY2GSjbHjHyOF6e1YVK8+ipSNe/TDekqJmNenJhoaMMecCRTdxsTdabHHI cmmCeJlDj/F8PKAokODmih7T85vH6cP4S32/nus4Hdnpp9Gdr42J7yDASpojrZFDMmFI Wr6DRC5dFiRSWRCMQkL1JPOZktCHuFH2HnIRUQvdzxvol/pMD8q2xmAQI4/uo3f8M+/C m9zg== X-Gm-Message-State: AGRZ1gKxg79TBhl5J+sRPIkWo5ZdB56CA1UY2lQMPULp5yQ08W20Jpf5 aVS1gDwMj9WQaVCEKKBKZYwnEaoM7l5Kt/mZ/CZYGg== X-Google-Smtp-Source: AJdET5fAoj0eGvOvr8dPoMtg3114bJR2EIjlFl76ZwQgdRl/p+FJiZCKB9JFrQMBcvrtF7gnii2XcMJIzDFs2A60fxg= X-Received: by 2002:ac8:7451:: with SMTP id h17mr21571570qtr.319.1542649965062; Mon, 19 Nov 2018 09:52:45 -0800 (PST) MIME-Version: 1.0 References: <1654420.p2kmoy7Ngz@xps> <26FA93C7ED1EAA44AB77D62FBE1D27BAB77BA42C@IRSMSX108.ger.corp.intel.com> <8CE3E05A3F976642AAB0F4675D0AD20E0B9BD2BC@SHSMSX101.ccr.corp.intel.com> In-Reply-To: From: Lincoln Lavoie Date: Mon, 19 Nov 2018 12:52:36 -0500 Message-ID: To: Jill Lovato Cc: Mara Bernazzani , lijuan.tu@intel.com, tim.odriscoll@intel.com, thomas@monjalon.net, Jeremy Plsek , ferruh.yigit@intel.com, ci@dpdk.org, marketing@dpdk.org, Patrick MacArthur Content-Type: multipart/alternative; boundary="0000000000002e4d1b057b082f87" Subject: Re: [dpdk-ci] [dpdk-marketing] Results are now public X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Nov 2018 17:52:46 -0000 --0000000000002e4d1b057b082f87 Content-Type: text/plain; charset="UTF-8" Hi Jill, Nope, that is Marion (in the hallway) and Michayla (our assistant director) in the machine room. I'll work with Mara to pull up a second picture of servers, etc. Cheers, Lincoln On Mon, Nov 19, 2018 at 12:49 PM Jill Lovato wrote: > Thank you, Mara. > > Couldn't help but notice in the picture that the girl inside the lab looks > an awful lot like the girl walking in the hallway - was this just a > coincidence, or has the photo been altered? Either way, can we get a second > image to add to the post, maybe a closer shot of the servers themselves? > > Thanks! > Jill > > On Mon, Nov 19, 2018 at 7:08 AM Mara Bernazzani > wrote: > >> Hello Jill, >> >> I apologize for the delay in getting back to you - attached is a picture >> you can use for the blog post. Let me know when its live and we will also >> share on our end. >> >> Thanks! >> Mara >> >> On Fri, Nov 16, 2018 at 11:42 AM Jill Lovato >> wrote: >> >>> Hi Lincoln, >>> >>> Thanks for the update. We'll plan to post the blog Monday afternoon or >>> Tuesday morning. >>> >>> Have a great weekend, >>> Jill >>> >>> On Thu, Nov 15, 2018 at 6:49 PM Lincoln Lavoie >>> wrote: >>> >>>> Hi All, >>>> >>>> Mara our marketing lead is out for a vacation this week. She's the >>>> keeper of all the good / approved pictures of the lab. Should be able to >>>> get you something early next week. >>>> >>>> Cheers, >>>> Lincoln >>>> >>>> On Thu, Nov 15, 2018 at 9:29 PM Tu, Lijuan wrote: >>>> >>>>> Agree, I would like to see some photos of the lab. >>>>> Should we add a brief introduction of contributors, this may attract >>>>> more companies or individual to contribute to the lab. >>>>> >>>>> > -----Original Message----- >>>>> > From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim >>>>> > Sent: Friday, November 16, 2018 6:14 AM >>>>> > To: Thomas Monjalon ; Jeremy Plsek >>>>> > >>>>> > Cc: Yigit, Ferruh ; ci@dpdk.org; >>>>> > marketing@dpdk.org; Lincoln Lavoie ; Patrick >>>>> > MacArthur >>>>> > Subject: Re: [dpdk-ci] [dpdk-marketing] Results are now public >>>>> > >>>>> > This looks good to me too. Some pictures would be nice, perhaps a >>>>> snapshot >>>>> > of the dashboard some of the hardware in the lab. It would be good >>>>> to get >>>>> > this posted on dpdk.org, and send a note to announce@dpdk.org to let >>>>> > people know about it. >>>>> > >>>>> > > -----Original Message----- >>>>> > > From: Thomas Monjalon [mailto:thomas@monjalon.net] >>>>> > > Sent: Wednesday, November 14, 2018 10:17 PM >>>>> > > To: Jeremy Plsek >>>>> > > Cc: O'Driscoll, Tim ; Yigit, Ferruh >>>>> > > ; ci@dpdk.org; marketing@dpdk.org; Lincoln >>>>> > > Lavoie ; Patrick MacArthur >>>>> > > >>>>> > > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public >>>>> > > >>>>> > > Looks great! >>>>> > > I think adding pictures would be nice for the blog. >>>>> > > Thank you >>>>> > > >>>>> > > 14/11/2018 22:07, Jeremy Plsek: >>>>> > > > With help from Lincoln and Patrick, below is an initial draft of >>>>> the >>>>> > > blog post. >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > DPDK Community Lab Publishes Relative Performance Testing Results >>>>> > > > >>>>> > > > The DPDK Community Lab is an open, independent testing resource >>>>> for >>>>> > > > the DPDK project. Its purpose is to perform automated testing on >>>>> > > > incoming patch submissions, to ensure the performance and >>>>> quality of >>>>> > > > DPDK is maintained. Participation in the lab is open to all DPDK >>>>> > > > project participants. >>>>> > > > >>>>> > > > For some time now, the DPDK Community Lab has been gathering >>>>> > > > performance deltas using the single-core packet I/O layer 2 >>>>> > > > throughput test from DTS for each patch series submitted to DPDK >>>>> > > > compared to the master branch. We are pleased to announce that >>>>> the >>>>> > > > Lab has recently been allowed to make these results public. These >>>>> > > > results are also now published to Patchwork as they are >>>>> > > > automatically generated. These results currently contain Mellanox >>>>> > > > and Intel devices, and the lab is able to support hardware from >>>>> any >>>>> > > > DPDK participants wishing to support these testing efforts. >>>>> > > > >>>>> > > > To view these results, you can go to DPDK Community Lab Dashboard >>>>> > > > via the following link: https://lab.dpdk.org. The dashboard >>>>> lists an >>>>> > > > overview of all active patch series and their results. Detailed >>>>> > > > results can be viewed by clicking on the patch series. If a patch >>>>> > > > fails to merge into master, a build log will show to help >>>>> identify >>>>> > > > any issues. If a patch cleanly merges into master, performance >>>>> delta >>>>> > > > results will show for each participating member. >>>>> > > > >>>>> > > > The Lab is hosted by the University of New Hampshire >>>>> > > > InterOperability Laboratory, as a neutral, third party location. >>>>> > > > This provides a secure environment for hosting equipment and >>>>> > > > generating unbiased results for all participating vendors. Lab >>>>> > > > participants, i.e. companies hosting equipment in the testing, >>>>> can >>>>> > > > securely access their equipment through a VPN, allowing for >>>>> > > > maintenance and performance tuning, as the DPDK project >>>>> progresses. >>>>> > > > >>>>> > > > The Lab works by polling the Patchwork API. When new patches are >>>>> > > > submitted, the CI server merges them with the master branch and >>>>> > > > generates a tarball. Each participating system unpacks and >>>>> installs >>>>> > > > the DPDK tarball and then runs the performance testing against >>>>> this >>>>> > > > DPDK build. When all systems have finished testing, the CI >>>>> gathers >>>>> > > > the results into our internal database to be shown on the >>>>> Dashboard, >>>>> > > > and sends final reports to Patchwork to show up on the submitted >>>>> patch. >>>>> > > > This allows patch submitters to utilize Patchwork to view their >>>>> > > > individual results, while also allowing anyone to quickly see an >>>>> > > > overview of results on the Dashboard. The system provides >>>>> > > > maintainers with positive confirmation of the stability and >>>>> > > > performance of the overall project. >>>>> > > > >>>>> > > > In the future, we plan to open the Lab to more testing scenarios, >>>>> > > > such as performance testing of other features, beyond single-core >>>>> > > > packet I/O layer 2 throughput, and possibly running Unit Tests >>>>> for DPDK. >>>>> > > > Additional features will be added to the Dashboard, such as >>>>> showing >>>>> > > > graphs of the performance changes of master over time. >>>>> > > > >>>>> > > > If your company would like to be involved, email the Continuous >>>>> > > > Integration group at ci@dpdk.org and dpdklab@iol.unh.edu. >>>>> > > > >>>>> > > > >>>>> > > > >>>>> > > > Thanks! >>>>> > > > >>>>> > > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek >>>> > >>>>> > > wrote: >>>>> > > > > >>>>> > > > > I can try to get it done later today, but I expect it to be >>>>> more >>>>> > > likely done on Monday. >>>>> > > > > >>>>> > > > > On Fri, Nov 9, 2018, 9:08 AM O'Driscoll, Tim >>>>> > > >>>> > > > >> >>>>> > > > >> >>>>> > > > >> >>>>> > > > >> > -----Original Message----- >>>>> > > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net] >>>>> > > > >> > Sent: Friday, November 9, 2018 2:02 PM >>>>> > > > >> > To: O'Driscoll, Tim >>>>> > > > >> > Cc: Yigit, Ferruh ; Jeremy Plsek >>>>> > > > >> > ; ci@dpdk.org; marketing@dpdk.org >>>>> > > > >> > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now >>>>> public >>>>> > > > >> > >>>>> > > > >> > 09/11/2018 14:58, O'Driscoll, Tim: >>>>> > > > >> > > From: Thomas Monjalon >>>>> > > > >> > > > 08/11/2018 14:01, Ferruh Yigit: >>>>> > > > >> > > > > On 11/7/2018 7:30 AM, Thomas Monjalon wrote: >>>>> > > > >> > > > > > 06/11/2018 16:33, Jeremy Plsek: >>>>> > > > >> > > > > >> Hi all, >>>>> > > > >> > > > > >> >>>>> > > > >> > > > > >> This is just an update that all detailed results >>>>> are >>>>> > > > >> > > > > >> now >>>>> > > > >> > public. >>>>> > > > >> > > > > >> >>>>> > > > >> > > > > >> If there is anything out of place, feel free to >>>>> let me >>>>> > > know! >>>>> > > > >> > > > > > >>>>> > > > >> > > > > > It is really nice! >>>>> > > > >> > > > > > Thank you >>>>> > > > >> > > > > >>>>> > > > >> > > > > Should we announce this in 'announce' or 'dev' mail >>>>> lists? >>>>> > > Many >>>>> > > > >> > people >>>>> > > > >> > > > not aware >>>>> > > > >> > > > > of this. >>>>> > > > >> > > > >>>>> > > > >> > > > It deserves an announce. >>>>> > > > >> > > > And even a blog post I guess. >>>>> > > > >> > > > +Cc marketing team >>>>> > > > >> > > >>>>> > > > >> > > Agreed. I can do a quick post to announce@dpdk.org. I >>>>> believe >>>>> > > Jeremy >>>>> > > > >> > is working on a blog post which can provide more detail. >>>>> > > > >> > >>>>> > > > >> > Should we wait to have a blog post and reference it in the >>>>> > > announce? >>>>> > > > >> >>>>> > > > >> Good question. I think it depends how long the blog will >>>>> take. If >>>>> > > we can do it fairly quickly, then this is a good idea. If it's >>>>> going >>>>> > > to take a few weeks, then we should announce it now. >>>>> > > > >> >>>>> > > > >> Jeremy: When do you think the blog will be ready? >>>>> > > > >> >>>>> > > > >>>>> > > > >>>>> > > > -- >>>>> > > > Jeremy Plsek >>>>> > > > UNH InterOperability Laboratory >>>>> > > > >>>>> > > >>>>> > > >>>>> > > >>>>> > > >>>>> >>>>> >>>> >>>> -- >>>> >>>> ******************************************************************************* >>>> *Lincoln Lavoie* >>>> Senior Engineer, Broadband Technologies >>>> >>>> >>>> www.iol.unh.edu >>>> 21 Madbury Rd., Ste. 100, Durham, NH 03824 >>>> Mobile: +1-603-674-2755 >>>> lylavoie@iol.unh.edu >>>> >>>> >>>> >>>> Ars sine scientia nihil est! -- Art without science is nothing. >>>> Scientia sine ars est vacua! -- Science without art is empty. >>>> >>>> Broadband Forum Gfast Certified Product List >>>> >>>> >>>> ******************************************************************************* >>>> >>> >>> >>> -- >>> *Jill Lovato* >>> Senior PR Manager >>> The Linux Foundation >>> jlovato@linuxfoundation.org >>> Skype: jill.lovato1 >>> Phone: +1.503.703.8268 >>> >> >> >> -- >> Mara Bernazzani >> Communications Coordinator >> UNH InterOperability Laboratory >> 21 Madbury Rd, Suite 100, Durham, NH 03824 >> mbernazzani@iol.unh.edu >> 1-603-862-0901 (o) >> [image: IOL Twitter] [image: IOL LinkedIn] >> [image: IOL Facebook] >> >> >> Interested to learn more? Sign up for our >> quarterly newsletter for industry news and IOL happenings. >> > > > -- > *Jill Lovato* > Senior PR Manager > The Linux Foundation > jlovato@linuxfoundation.org > Skype: jill.lovato1 > Phone: +1.503.703.8268 > -- ******************************************************************************* *Lincoln Lavoie* Senior Engineer, Broadband Technologies www.iol.unh.edu 21 Madbury Rd., Ste. 100, Durham, NH 03824 Mobile: +1-603-674-2755 lylavoie@iol.unh.edu Ars sine scientia nihil est! -- Art without science is nothing. Scientia sine ars est vacua! -- Science without art is empty. Broadband Forum Gfast Certified Product List ******************************************************************************* --0000000000002e4d1b057b082f87 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi = Jill,

Nope, that is Mario= n (in the hallway) and Michayla (our assistant director) in the machine roo= m.

I'll work with Mar= a to pull up a second picture of servers, etc.

Cheers,
Lincoln

On Mon, Nov 19, 2018 at 12:49 PM Jill Lovato <jlovato@linuxfoundation.org> wrote:
Thank you, Mara.=C2= =A0

Couldn't help but notice in the picture that the= girl inside the lab looks an awful lot like the girl walking in the hallwa= y - was this just a coincidence, or has the photo been altered? Either way,= can we get a second image to add to the post, maybe a closer shot of the s= ervers themselves?=C2=A0

Thanks!
Jill
On Mon, Nov 19, 2018 at = 7:08 AM Mara Bernazzani <mbernazzani@iol.unh.edu> wrote:
Hello Jill,

I apologi= ze for the delay in getting back to you - attached is a picture you can use= for the blog post. Let me know when its live and we will also share on our= end.

Thanks!
Mara

On Fri, Nov 16, 2018 at 11:42 AM Jill= Lovato <jlovato@linuxfoundation.org> wrote:
Hi Lincoln,

Thanks for the update. We'll plan to post the blog Monday afternoon o= r Tuesday morning.=C2=A0

Have a great weekend,
Jill

On T= hu, Nov 15, 2018 at 6:49 PM Lincoln Lavoie <lylavoie@iol.unh.edu> wrote:
=
Hi All,

Mara our marketing lead is out for a vacat= ion this week.=C2=A0 She's the keeper of all the good / approved pictur= es of the lab.=C2=A0 Should be able to get you something early=C2=A0next we= ek.

Cheers,
Lincoln

On Thu, Nov 15, 2018 at 9:29 PM Tu, Lijuan <lijuan.tu@intel.com> wrote:
Agree, I would lik= e to see some photos of the lab.
Should we add a brief introduction of contributors, this may attract more c= ompanies or individual to contribute to the lab.

> -----Original Message-----
> From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
> Sent: Friday, November 16, 2018 6:14 AM
> To: Thomas Monjalon <thomas@monjalon.net>; Jeremy Plsek
> <jplsek@iol= .unh.edu>
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org;
> marketing@dpdk= .org; Lincoln Lavoie <lylavoie@iol.unh.edu>; Patrick
> MacArthur <pmacarth@iol.unh.edu>
> Subject: Re: [dpdk-ci] [dpdk-marketing] Results are now public
>
> This looks good to me too. Some pictures would be nice, perhaps a snap= shot
> of the dashboard some of the hardware in the lab. It would be good to = get
> this posted on dpdk.org, and send a note to announce@dpdk.org to let
> people know about it.
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > Sent: Wednesday, November 14, 2018 10:17 PM
> > To: Jeremy Plsek <jplsek@iol.unh.edu>
> > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Yigit, Ferruh
> > <f= erruh.yigit@intel.com>; ci@dpdk.org; marketing@dpdk.org; Lincoln
> > Lavoie <lylavoie@iol.unh.edu>; Patrick MacArthur
> > <pma= carth@iol.unh.edu>
> > Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public > >
> > Looks great!
> > I think adding pictures would be nice for the blog.
> > Thank you
> >
> > 14/11/2018 22:07, Jeremy Plsek:
> > > With help from Lincoln and Patrick, below is an initial draf= t of the
> > blog post.
> > >
> > >
> > >
> > > DPDK Community Lab Publishes Relative Performance Testing Re= sults
> > >
> > > The DPDK Community Lab is an open, independent testing resou= rce for
> > > the DPDK project. Its purpose is to perform automated testin= g on
> > > incoming patch submissions, to ensure the performance and qu= ality of
> > > DPDK is maintained. Participation in the lab is open to all = DPDK
> > > project participants.
> > >
> > > For some time now, the DPDK Community Lab has been gathering=
> > > performance deltas using the single-core packet I/O layer 2<= br> > > > throughput test from DTS for each patch series submitted to = DPDK
> > > compared to the master branch. We are pleased to announce th= at the
> > > Lab has recently been allowed to make these results public. = These
> > > results are also now published to Patchwork as they are
> > > automatically generated. These results currently contain Mel= lanox
> > > and Intel devices, and the lab is able to support hardware f= rom any
> > > DPDK participants wishing to support these testing efforts.<= br> > > >
> > > To view these results, you can go to DPDK Community Lab Dash= board
> > > via the following link: https://lab.dpdk.org. The dashboard l= ists an
> > > overview of all active patch series and their results. Detai= led
> > > results can be viewed by clicking on the patch series. If a = patch
> > > fails to merge into master, a build log will show to help id= entify
> > > any issues. If a patch cleanly merges into master, performan= ce delta
> > > results will show for each participating member.
> > >
> > > The Lab is hosted by the University of New Hampshire
> > > InterOperability Laboratory, as a neutral, third party locat= ion.
> > > This provides a secure environment for hosting equipment and=
> > > generating unbiased results for all participating vendors. L= ab
> > > participants, i.e. companies hosting equipment in the testin= g, can
> > > securely access their equipment through a VPN, allowing for<= br> > > > maintenance and performance tuning, as the DPDK project prog= resses.
> > >
> > > The Lab works by polling the Patchwork API. When new patches= are
> > > submitted, the CI server merges them with the master branch = and
> > > generates a tarball. Each participating system unpacks and i= nstalls
> > > the DPDK tarball and then runs the performance testing again= st this
> > > DPDK build. When all systems have finished testing, the CI g= athers
> > > the results into our internal database to be shown on the Da= shboard,
> > > and sends final reports to Patchwork to show up on the submi= tted patch.
> > > This allows patch submitters to utilize Patchwork to view th= eir
> > > individual results, while also allowing anyone to quickly se= e an
> > > overview of results on the Dashboard. The system provides > > > maintainers with positive confirmation of the stability and<= br> > > > performance of the overall project.
> > >
> > > In the future, we plan to open the Lab to more testing scena= rios,
> > > such as performance testing of other features, beyond single= -core
> > > packet I/O layer 2 throughput, and possibly running Unit Tes= ts for DPDK.
> > > Additional features will be added to the Dashboard, such as = showing
> > > graphs of the performance changes of master over time.
> > >
> > > If your company would like to be involved, email the Continu= ous
> > > Integration group at ci@dpdk.org and dpdklab@iol.unh.edu.
> > >
> > >
> > >
> > > Thanks!
> > >
> > > On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek <jplsek@iol.unh.edu>
> > wrote:
> > > >
> > > > I can try to get it done later today, but I expect it t= o be more
> > likely done on Monday.
> > > >
> > > > On Fri, Nov 9, 2018, 9:08 AM O'Driscoll, Tim
> > <= tim.odriscoll@intel.com wrote:
> > > >>
> > > >>
> > > >>
> > > >> > -----Original Message-----
> > > >> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > >> > Sent: Friday, November 9, 2018 2:02 PM
> > > >> > To: O'Driscoll, Tim <tim.odriscoll@intel.com><= br> > > > >> > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Jeremy = Plsek
> > > >> > <jplsek@iol.unh.edu>; ci@dpdk.org; marketing@dpdk.org
> > > >> > Subject: Re: [dpdk-marketing] [dpdk-ci] Result= s are now public
> > > >> >
> > > >> > 09/11/2018 14:58, O'Driscoll, Tim:
> > > >> > > From: Thomas Monjalon
> > > >> > > > 08/11/2018 14:01, Ferruh Yigit:
> > > >> > > > > On 11/7/2018 7:30 AM, Thomas Mo= njalon wrote:
> > > >> > > > > > 06/11/2018 16:33, Jeremy P= lsek:
> > > >> > > > > >> Hi all,
> > > >> > > > > >>
> > > >> > > > > >> This is just an update= that all detailed results are
> > > >> > > > > >> now
> > > >> > public.
> > > >> > > > > >>
> > > >> > > > > >> If there is anything o= ut of place, feel free to let me
> > know!
> > > >> > > > > >
> > > >> > > > > > It is really nice!
> > > >> > > > > > Thank you
> > > >> > > > >
> > > >> > > > > Should we announce this in '= ;announce' or 'dev' mail lists?
> > Many
> > > >> > people
> > > >> > > > not aware
> > > >> > > > > of this.
> > > >> > > >
> > > >> > > > It deserves an announce.
> > > >> > > > And even a blog post I guess.
> > > >> > > > +Cc marketing team
> > > >> > >
> > > >> > > Agreed. I can do a quick post to announce@dpdk.org. I be= lieve
> > Jeremy
> > > >> > is working on a blog post which can provide mo= re detail.
> > > >> >
> > > >> > Should we wait to have a blog post and referen= ce it in the
> > announce?
> > > >>
> > > >> Good question. I think it depends how long the blog= will take. If
> > we can do it fairly quickly, then this is a good idea. If it'= s going
> > to take a few weeks, then we should announce it now.
> > > >>
> > > >> Jeremy: When do you think the blog will be ready? > > > >>
> > >
> > >
> > > --
> > > Jeremy Plsek
> > > UNH InterOperability Laboratory
> > >
> >
> >
> >
> >



--
<= div dir=3D"ltr">
**************************************************************= *****************
Lincoln Lavoie
= Senior Engineer, Broadband Technologies


2= 1 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755=
=C2=A0=C2=A0=C2=A0=C2=A0

Ars sine scientia nihil est! -- Art without science= is nothing.
Scientia sine ars est vacua! -- Science without = art is empty.

*********************************************= **********************************
=


--
Jil= l Lovato
Senior PR Manage= r
The Linux Foundation
Skype:= jill.lovato1
Phone: +1.503.703.82= 68


--
=
Mara Bernazzani
Communications Coordinator
=
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, = Durham, NH 03824
1-603-862-0901 (o)
=
3D"=C2=A03D"IOL=C2=A03D"IOL=

Interested= to learn more? Sign up= for our quarterly newsletter for industry news and IOL happenings.


--
Jill Lovato
Senior PR Manager
The Linux Foundation
Skype: jill.lovato1
Phone: +1.503.703.8268


--
*********************************************************************= **********
Lincoln Lavoie
Senior = Engineer, Broadband Technologies


21 Madbury Rd., Ste. 100, Durham, NH 03824
Mobile: +1-603-674-2755
=C2=A0=C2=A0<= a href=3D"https://twitter.com/#!/UNH_IOL" target=3D"_blank">=C2=A0=C2=A0

Ars= sine scientia nihil est! -- Art without science is nothing.
= Scientia sine ars est vacua! -- Science without art is empty.
************************************************************= *******************
--0000000000002e4d1b057b082f87--