DPDK CI discussions
 help / color / Atom feed
From: Jill Lovato <jlovato@linuxfoundation.org>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	jplsek@iol.unh.edu, ferruh.yigit@intel.com,  ci@dpdk.org,
	marketing@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
	 pmacarth@iol.unh.edu
Subject: Re: [dpdk-ci] [dpdk-marketing]  Results are now public
Date: Thu, 15 Nov 2018 14:30:54 -0800
Message-ID: <CANA499Eya9Y+7evKLW4Nzz1ZuXw9j4OXjPXhG1V8yR-90ztXOQ@mail.gmail.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB77BA42C@IRSMSX108.ger.corp.intel.com>

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

Agree on the draft - thank you, Jeremy, for putting this together!

I haven't seen any photos of the lab - can someone point me in the right
direction, or perhaps snap and few and share on this thread? I can get this
posted to the DPDK site as early as tomorrow (Friday) morning.

Many thanks,
Jill

On Thu, Nov 15, 2018 at 2:13 PM O'Driscoll, Tim <tim.odriscoll@intel.com>
wrote:

> 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 <jplsek@iol.unh.edu>
> > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; 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-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 <jplsek@iol.unh.edu>
> > 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
> > <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>
> > > >> > 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] 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
> > >
> >
> >
> >
> >
>
>

-- 
*Jill Lovato*
Senior PR Manager
The Linux Foundation
jlovato@linuxfoundation.org
Skype: jill.lovato1
Phone: +1.503.703.8268

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

<div dir="ltr">Agree on the draft - thank you, Jeremy, for putting this together!<div><br></div><div>I haven&#39;t seen any photos of the lab - can someone point me in the right direction, or perhaps snap and few and share on this thread? I can get this posted to the DPDK site as early as tomorrow (Friday) morning. </div><div><br></div><div>Many thanks,</div><div>Jill</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Nov 15, 2018 at 2:13 PM O&#39;Driscoll, Tim &lt;<a href="mailto:tim.odriscoll@intel.com">tim.odriscoll@intel.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 <a href="http://dpdk.org" rel="noreferrer" target="_blank">dpdk.org</a>, and send a note to <a href="mailto:announce@dpdk.org" target="_blank">announce@dpdk.org</a> to let people know about it.<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Thomas Monjalon [mailto:<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>]<br>
&gt; Sent: Wednesday, November 14, 2018 10:17 PM<br>
&gt; To: Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;<br>
&gt; Cc: O&#39;Driscoll, Tim &lt;<a href="mailto:tim.odriscoll@intel.com" target="_blank">tim.odriscoll@intel.com</a>&gt;; Yigit, Ferruh<br>
&gt; &lt;<a href="mailto:ferruh.yigit@intel.com" target="_blank">ferruh.yigit@intel.com</a>&gt;; <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a>; <a href="mailto:marketing@dpdk.org" target="_blank">marketing@dpdk.org</a>; Lincoln<br>
&gt; Lavoie &lt;<a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a>&gt;; Patrick MacArthur &lt;<a href="mailto:pmacarth@iol.unh.edu" target="_blank">pmacarth@iol.unh.edu</a>&gt;<br>
&gt; Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public<br>
&gt; <br>
&gt; Looks great!<br>
&gt; I think adding pictures would be nice for the blog.<br>
&gt; Thank you<br>
&gt; <br>
&gt; 14/11/2018 22:07, Jeremy Plsek:<br>
&gt; &gt; With help from Lincoln and Patrick, below is an initial draft of the<br>
&gt; blog post.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; DPDK Community Lab Publishes Relative Performance Testing Results<br>
&gt; &gt;<br>
&gt; &gt; The DPDK Community Lab is an open, independent testing resource for<br>
&gt; &gt; the DPDK project. Its purpose is to perform automated testing on<br>
&gt; &gt; incoming patch submissions, to ensure the performance and quality of<br>
&gt; &gt; DPDK is maintained. Participation in the lab is open to all DPDK<br>
&gt; &gt; project participants.<br>
&gt; &gt;<br>
&gt; &gt; For some time now, the DPDK Community Lab has been gathering<br>
&gt; &gt; performance deltas using the single-core packet I/O layer 2 throughput<br>
&gt; &gt; test from DTS for each patch series submitted to DPDK compared to the<br>
&gt; &gt; master branch. We are pleased to announce that the Lab has recently<br>
&gt; &gt; been allowed to make these results public. These results are also now<br>
&gt; &gt; published to Patchwork as they are automatically generated. These<br>
&gt; &gt; results currently contain Mellanox and Intel devices, and the lab is<br>
&gt; &gt; able to support hardware from any DPDK participants wishing to support<br>
&gt; &gt; these testing efforts.<br>
&gt; &gt;<br>
&gt; &gt; To view these results, you can go to DPDK Community Lab Dashboard via<br>
&gt; &gt; the following link: <a href="https://lab.dpdk.org" rel="noreferrer" target="_blank">https://lab.dpdk.org</a>. The dashboard lists an<br>
&gt; &gt; overview of all active patch series and their results. Detailed<br>
&gt; &gt; results can be viewed by clicking on the patch series. If a patch<br>
&gt; &gt; fails to merge into master, a build log will show to help identify any<br>
&gt; &gt; issues. If a patch cleanly merges into master, performance delta<br>
&gt; &gt; results will show for each participating member.<br>
&gt; &gt;<br>
&gt; &gt; The Lab is hosted by the University of New Hampshire InterOperability<br>
&gt; &gt; Laboratory, as a neutral, third party location. This provides a secure<br>
&gt; &gt; environment for hosting equipment and generating unbiased results for<br>
&gt; &gt; all participating vendors. Lab participants, i.e. companies hosting<br>
&gt; &gt; equipment in the testing, can securely access their equipment through<br>
&gt; &gt; a VPN, allowing for maintenance and performance tuning, as the DPDK<br>
&gt; &gt; project progresses.<br>
&gt; &gt;<br>
&gt; &gt; The Lab works by polling the Patchwork API. When new patches are<br>
&gt; &gt; submitted, the CI server merges them with the master branch and<br>
&gt; &gt; generates a tarball. Each participating system unpacks and installs<br>
&gt; &gt; the DPDK tarball and then runs the performance testing against this<br>
&gt; &gt; DPDK build. When all systems have finished testing, the CI gathers the<br>
&gt; &gt; results into our internal database to be shown on the Dashboard, and<br>
&gt; &gt; sends final reports to Patchwork to show up on the submitted patch.<br>
&gt; &gt; This allows patch submitters to utilize Patchwork to view their<br>
&gt; &gt; individual results, while also allowing anyone to quickly see an<br>
&gt; &gt; overview of results on the Dashboard. The system provides maintainers<br>
&gt; &gt; with positive confirmation of the stability and performance of the<br>
&gt; &gt; overall project.<br>
&gt; &gt;<br>
&gt; &gt; In the future, we plan to open the Lab to more testing scenarios, such<br>
&gt; &gt; as performance testing of other features, beyond single-core packet<br>
&gt; &gt; I/O layer 2 throughput, and possibly running Unit Tests for DPDK.<br>
&gt; &gt; Additional features will be added to the Dashboard, such as showing<br>
&gt; &gt; graphs of the performance changes of master over time.<br>
&gt; &gt;<br>
&gt; &gt; If your company would like to be involved, email the Continuous<br>
&gt; &gt; Integration group at <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a> and <a href="mailto:dpdklab@iol.unh.edu" target="_blank">dpdklab@iol.unh.edu</a>.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Thanks!<br>
&gt; &gt;<br>
&gt; &gt; On Fri, Nov 9, 2018 at 10:03 AM Jeremy Plsek &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;<br>
&gt; wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I can try to get it done later today, but I expect it to be more<br>
&gt; likely done on Monday.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On Fri, Nov 9, 2018, 9:08 AM O&#39;Driscoll, Tim<br>
&gt; &lt;<a href="mailto:tim.odriscoll@intel.com" target="_blank">tim.odriscoll@intel.com</a> wrote:<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; &gt; -----Original Message-----<br>
&gt; &gt; &gt;&gt; &gt; From: Thomas Monjalon [mailto:<a href="mailto:thomas@monjalon.net" target="_blank">thomas@monjalon.net</a>]<br>
&gt; &gt; &gt;&gt; &gt; Sent: Friday, November 9, 2018 2:02 PM<br>
&gt; &gt; &gt;&gt; &gt; To: O&#39;Driscoll, Tim &lt;<a href="mailto:tim.odriscoll@intel.com" target="_blank">tim.odriscoll@intel.com</a>&gt;<br>
&gt; &gt; &gt;&gt; &gt; Cc: Yigit, Ferruh &lt;<a href="mailto:ferruh.yigit@intel.com" target="_blank">ferruh.yigit@intel.com</a>&gt;; Jeremy Plsek<br>
&gt; &gt; &gt;&gt; &gt; &lt;<a href="mailto:jplsek@iol.unh.edu" target="_blank">jplsek@iol.unh.edu</a>&gt;; <a href="mailto:ci@dpdk.org" target="_blank">ci@dpdk.org</a>; <a href="mailto:marketing@dpdk.org" target="_blank">marketing@dpdk.org</a><br>
&gt; &gt; &gt;&gt; &gt; Subject: Re: [dpdk-marketing] [dpdk-ci] Results are now public<br>
&gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt;&gt; &gt; 09/11/2018 14:58, O&#39;Driscoll, Tim:<br>
&gt; &gt; &gt;&gt; &gt; &gt; From: Thomas Monjalon<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; 08/11/2018 14:01, Ferruh Yigit:<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; On 11/7/2018 7:30 AM, Thomas Monjalon wrote:<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; 06/11/2018 16:33, Jeremy Plsek:<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt; Hi all,<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt; This is just an update that all detailed results are now<br>
&gt; &gt; &gt;&gt; &gt; public.<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;&gt; If there is anything out of place, feel free to let me<br>
&gt; know!<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; It is really nice!<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; &gt; Thank you<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; Should we announce this in &#39;announce&#39; or &#39;dev&#39; mail lists?<br>
&gt; Many<br>
&gt; &gt; &gt;&gt; &gt; people<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; not aware<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; &gt; of this.<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; It deserves an announce.<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; And even a blog post I guess.<br>
&gt; &gt; &gt;&gt; &gt; &gt; &gt; +Cc marketing team<br>
&gt; &gt; &gt;&gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; &gt; &gt; Agreed. I can do a quick post to <a href="mailto:announce@dpdk.org" target="_blank">announce@dpdk.org</a>. I believe<br>
&gt; Jeremy<br>
&gt; &gt; &gt;&gt; &gt; is working on a blog post which can provide more detail.<br>
&gt; &gt; &gt;&gt; &gt;<br>
&gt; &gt; &gt;&gt; &gt; Should we wait to have a blog post and reference it in the<br>
&gt; announce?<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Good question. I think it depends how long the blog will take. If<br>
&gt; we can do it fairly quickly, then this is a good idea. If it&#39;s going to<br>
&gt; take a few weeks, then we should announce it now.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; Jeremy: When do you think the blog will be ready?<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; Jeremy Plsek<br>
&gt; &gt; UNH InterOperability Laboratory<br>
&gt; &gt;<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font color="#999999"><strong>Jill Lovato</strong></font></div><div><font color="#999999">Senior PR Manager </font></div><div><font color="#999999">The Linux Foundation</font></div><div><a href="mailto:jlovato@linuxfoundation.org" target="_blank">jlovato@linuxfoundation.org</a> </div><div><font color="#999999">Skype: jill.lovato1</font></div><div><font color="#999999">Phone: +1.503.703.8268</font></div></div></div></div></div></div></div></div>

  reply index

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 15:33 [dpdk-ci] " Jeremy Plsek
2018-11-07  7:30 ` Thomas Monjalon
2018-11-08 13:01   ` Ferruh Yigit
2018-11-08 13:10     ` Thomas Monjalon
2018-11-08 13:16       ` [dpdk-ci] [dpdk-marketing] " Trishan de Lanerolle
2018-11-08 13:37         ` Thomas Monjalon
2018-11-08 15:57         ` Jeremy Plsek
2018-11-09 13:58       ` O'Driscoll, Tim
2018-11-09 14:01         ` Thomas Monjalon
2018-11-09 14:07           ` Trishan de Lanerolle
2018-11-09 14:08           ` O'Driscoll, Tim
2018-11-09 15:03             ` Jeremy Plsek
2018-11-14 21:07               ` Jeremy Plsek
2018-11-14 22:16                 ` Thomas Monjalon
2018-11-15 22:13                   ` O'Driscoll, Tim
2018-11-15 22:30                     ` Jill Lovato [this message]
2018-11-16  2:29                     ` Tu, Lijuan
2018-11-16  2:48                       ` Lincoln Lavoie
2018-11-16 16:42                         ` Jill Lovato
2018-11-19 15:08                           ` Mara Bernazzani
2018-11-19 17:48                             ` Jill Lovato
2018-11-19 17:52                               ` Lincoln Lavoie
2018-11-19 17:55                                 ` Jill Lovato
2018-11-20  9:40                                   ` Thomas Monjalon
2018-11-20 13:58                                   ` O'Driscoll, Tim
2018-11-20 15:35                                     ` Jeremy Plsek

Reply instructions:

You may reply publically 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=CANA499Eya9Y+7evKLW4Nzz1ZuXw9j4OXjPXhG1V8yR-90ztXOQ@mail.gmail.com \
    --to=jlovato@linuxfoundation.org \
    --cc=ci@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jplsek@iol.unh.edu \
    --cc=lylavoie@iol.unh.edu \
    --cc=marketing@dpdk.org \
    --cc=pmacarth@iol.unh.edu \
    --cc=thomas@monjalon.net \
    --cc=tim.odriscoll@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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox