From john.mcnamara at intel.com Thu Mar 1 10:44:19 2018 From: john.mcnamara at intel.com (Mcnamara, John) Date: Thu, 1 Mar 2018 09:44:19 +0000 Subject: [dpdk-web] [PATCH v2] update roadmap for 18.05 In-Reply-To: <20180228085104.2665-1-brian.archbold@intel.com> References: <20180228085104.2665-1-brian.archbold@intel.com> Message-ID: > -----Original Message----- > From: web [mailto:web-bounces at dpdk.org] On Behalf Of Brian Archbold > Sent: Wednesday, February 28, 2018 8:51 AM > To: web at dpdk.org > Cc: Archbold, Brian > Subject: [dpdk-web] [PATCH v2] update roadmap for 18.05 > > Signed-off-by: Brian Archbold Acked-by: John McNamara From thomas at monjalon.net Tue Mar 6 12:25:44 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Tue, 06 Mar 2018 12:25:44 +0100 Subject: [dpdk-web] [RFC v2] Add LTS section on the roadmap page In-Reply-To: <20180209130440.20380-1-bluca@debian.org> References: <20180208182142.6189-1-bluca@debian.org> <20180209130440.20380-1-bluca@debian.org> Message-ID: <3266586.a8klAloIbi@xps> Hi Luca, Sorry I forgot this patch you sent one month ago. 09/02/2018 14:04, Luca Boccassi: > +

Stable releases

> +

Stable point releases follow mainline releases. > +

After each -rc tag and after the final version, relevant bug fixes get > + backported by the stable maintainers into the respective branches in "bursts". > +

Developers can provide stable-specific patches by sending them to stable at dpdk.org > + only (avoiding dev at dpdk.org). > +

After all the relevant bugfixes have been backported, regression tests are ran, > + and if clear, the stable release is announced. > +

Typically a new stable release version follows a mainline release by 1-2 weeks, depending > + on the test results. It is a good description of the current process. When this patch is applied, I would like to discuss having a first stable release before the next major release. > +

Stable releases roadmap

No need for this title if below is a table. > +

16.11 is an LTS release, and is going to be maintained by Luca Boccassi until the end of > + 2018, with the latest point release following the release of 18.11 in November 2018. > +

17.11 is an LTS release, and is going to be maintained by Yuanhan Liu until the end of > + 2019, with the latest point release following the release of 19.11 in November 2019. We should include non LTS releases and make it a table: branch next version date end of life maintainer From thomas at monjalon.net Tue Mar 6 18:02:00 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Tue, 06 Mar 2018 18:02:00 +0100 Subject: [dpdk-web] [PATCH] add sponsors of India summit In-Reply-To: <20180209213418.20141-1-thomas@monjalon.net> References: <20180209213418.20141-1-thomas@monjalon.net> Message-ID: <3767347.IUrVXCMsQY@xps> 09/02/2018 22:34, Thomas Monjalon: > Suggested-by: Trishan de Lanerolle > Signed-off-by: Thomas Monjalon > --- > +


> +
    > +
  • Sponsors (in addition to membership): > +
  • F5 > +
  • Intel > +
> +
Applied From bluca at debian.org Tue Mar 6 20:43:54 2018 From: bluca at debian.org (Luca Boccassi) Date: Tue, 6 Mar 2018 19:43:54 +0000 Subject: [dpdk-web] [RFC v3] Add LTS section on the roadmap page In-Reply-To: <20180209130440.20380-1-bluca@debian.org> References: <20180209130440.20380-1-bluca@debian.org> Message-ID: <20180306194354.19891-1-bluca@debian.org> Signed-off-by: Luca Boccassi --- dev/roadmap.html | 36 +++++++++++++++++++++++++++++++++++- 1 file changed, 35 insertions(+), 1 deletion(-) diff --git a/dev/roadmap.html b/dev/roadmap.html index 569d8b8..ebb81a9 100644 --- a/dev/roadmap.html +++ b/dev/roadmap.html @@ -37,7 +37,7 @@ -
+

Development roadmap

Major known features and milestones may be noted here. This list is obviously neither complete nor guaranteed. @@ -96,5 +96,39 @@

  • Integration deadline: October 5, 2018
  • Release: November 2, 2018 +

    Stable releases

    +

    Stable point releases follow mainline releases. +

    After each -rc tag and after the final version, relevant bug fixes get + backported by the stable maintainers into the respective branches in "bursts". +

    Developers can provide stable-specific patches by sending them to stable at dpdk.org + only (avoiding dev at dpdk.org). +

    After all the relevant bugfixes have been backported, regression tests are ran, + and if clear, the stable release is announced. +

    Typically a new stable release version follows a mainline release by 1-2 weeks, depending + on the test results. +


    + + + + + + + + + + + + + + + + + + + + + + +
    BranchNext versionDateEnd of lifeMaintainer
    16.1116.11.6May 19, 2018November 2018Luca Boccassi
    17.1117.11.2May 19, 2018November 2019Yuanhan Liu
  • -- 2.14.2 From bluca at debian.org Tue Mar 6 20:45:00 2018 From: bluca at debian.org (Luca Boccassi) Date: Tue, 06 Mar 2018 19:45:00 +0000 Subject: [dpdk-web] [RFC v2] Add LTS section on the roadmap page In-Reply-To: <3266586.a8klAloIbi@xps> References: <20180208182142.6189-1-bluca@debian.org> <20180209130440.20380-1-bluca@debian.org> <3266586.a8klAloIbi@xps> Message-ID: <1520365500.27712.42.camel@debian.org> On Tue, 2018-03-06 at 12:25 +0100, Thomas Monjalon wrote: > Hi Luca, > > Sorry I forgot this patch you sent one month ago. No worries. > 09/02/2018 14:04, Luca Boccassi: > > +

    Stable releases

    > > +

    Stable point releases follow mainline releases. > > +

    After each -rc tag and after the final version, > > relevant bug fixes get > > +????????backported by the stable maintainers into the respective > > branches in "bursts". > > +

    Developers can provide stable-specific patches by > > sending them to stable at dpdk.org > > +????????only (avoiding dev at dpdk.org). > > +

    After all the relevant bugfixes have been backported, > > regression tests are ran, > > +????????and if clear, the stable release is announced. > > +

    Typically a new stable release version follows a > > mainline release by 1-2 weeks, depending > > +????????on the test results. > > It is a good description of the current process. > When this patch is applied, I would like to discuss having a first > stable release before the next major release. Ok! > > +

    Stable releases roadmap

    > > No need for this title if below is a table. > > > +

    16.11 is an LTS release, and is going to be maintained > > by Luca Boccassi until the end of > > +????????2018, with the latest point release following the release > > of 18.11 in November 2018. > > +

    17.11 is an LTS release, and is going to be maintained > > by Yuanhan Liu until the end of > > +????????2019, with the latest point release following the release > > of 19.11 in November 2019. > > We should include non LTS releases and make it a table: > branch????next version????date????end of life????maintainer Ok, done in v3, please have a look. The release dates are tentative of course - I picked the mainline release + 2 weeks. -- Kind regards, Luca Boccassi From bluca at debian.org Wed Mar 7 15:09:43 2018 From: bluca at debian.org (Luca Boccassi) Date: Wed, 7 Mar 2018 14:09:43 +0000 Subject: [dpdk-web] [PATCH] release 16.11.5 Message-ID: <20180307140943.778-1-bluca@debian.org> Signed-off-by: Luca Boccassi --- rel.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rel.html b/rel.html index f905401..2c73b03 100644 --- a/rel.html +++ b/rel.html @@ -85,9 +85,9 @@

    cbdf8b7a92ce934d47c38cbc9c20c54a
    - DPDK 16.11.4 (LTS) - 2017 December 8 -
    ad756810aac6c6d9329ecead1680aceb
    + DPDK 16.11.5 (LTS) + 2018 March 7 +
    0fafaca7948ebdd11d7d388b06b21d56
    DPDK 16.07.2 -- 2.14.2 From thomas at monjalon.net Wed Mar 7 15:42:18 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Wed, 07 Mar 2018 15:42:18 +0100 Subject: [dpdk-web] [PATCH] release 16.11.5 In-Reply-To: <20180307140943.778-1-bluca@debian.org> References: <20180307140943.778-1-bluca@debian.org> Message-ID: <19524570.rv8MGE5eUP@xps> 07/03/2018 15:09, Luca Boccassi: > Signed-off-by: Luca Boccassi Applied, thanks for the new release! From ed.czeck at atomicrules.com Thu Mar 8 14:07:29 2018 From: ed.czeck at atomicrules.com (Ed Czeck) Date: Thu, 8 Mar 2018 08:07:29 -0500 Subject: [dpdk-web] [PATCH] Remove ARM support for ark from roadmap Message-ID: <1520514449-4543-1-git-send-email-ed.czeck@atomicrules.com> Signed-off-by: Ed Czeck --- dev/roadmap.html | 1 - 1 file changed, 1 deletion(-) diff --git a/dev/roadmap.html b/dev/roadmap.html index 569d8b8..88559e7 100644 --- a/dev/roadmap.html +++ b/dev/roadmap.html @@ -48,7 +48,6 @@
  • new device specification (devargs) syntax
  • secondary process support in virtual devices
  • ethdev port representor driver -
  • ARM support for ark
  • mlx5 IPsec offload
  • virtio-crypto driver
  • eventdev ordered and atomic queues for DPAA2 -- 2.7.4 From john.mcnamara at intel.com Thu Mar 8 14:12:57 2018 From: john.mcnamara at intel.com (Mcnamara, John) Date: Thu, 8 Mar 2018 13:12:57 +0000 Subject: [dpdk-web] [PATCH] Remove ARM support for ark from roadmap In-Reply-To: <1520514449-4543-1-git-send-email-ed.czeck@atomicrules.com> References: <1520514449-4543-1-git-send-email-ed.czeck@atomicrules.com> Message-ID: > -----Original Message----- > From: web [mailto:web-bounces at dpdk.org] On Behalf Of Ed Czeck > Sent: Thursday, March 8, 2018 1:07 PM > To: web at dpdk.org > Cc: john.miller at atomicrules.com; shepard.siegel at atomicrules.com; Yigit, > Ferruh ; Ed Czeck > Subject: [dpdk-web] [PATCH] Remove ARM support for ark from roadmap > > Signed-off-by: Ed Czeck Acked-by: John McNamara From thomas at monjalon.net Thu Mar 8 23:25:32 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Thu, 08 Mar 2018 23:25:32 +0100 Subject: [dpdk-web] [PATCH v2] update roadmap for 18.05 In-Reply-To: <20180228085104.2665-1-brian.archbold@intel.com> References: <20180228085104.2665-1-brian.archbold@intel.com> Message-ID: <2933639.xypejkkKWr@xps> Hi, 28/02/2018 09:51, Brian Archbold: > Signed-off-by: Brian Archbold > --- >

    Version 18.05 (2018 May)

    >
      > -
    • memory management rework > -
    • hotplug > -
    • new device specification (devargs) syntax > -
    • secondary process support in virtual devices > -
    • ethdev port representor driver > -
    • ARM support for ark > -
    • mlx5 IPsec offload > -
    • virtio-crypto driver > -
    • eventdev ordered and atomic queues for DPAA2 > -
    • eventdev crypto adapter > -
    • libedit integration > +
    • selective datapath in the vhost-user library > +
    • new Intel device driver (IFC VF) for accelerated virtio data path > +
    • interrupt mode for vhost > +
    • virtio-user for virtio-crypto > +
    • ethdev API to for recommended descriptor ring sizes > +
    • memory subsystem improvements > +
    • ip pipeline enhancements > +
    • new API to support hardware and software compression and decompression > +
    • new API to manage tunnel endpoints > +
    • port representor, a virtual PMD with a logical representation of any port > +
    • add PPPoE/PPPoL2Tv2 to I40e PMD > +
    • update Intel PMDs for Rx/Tx offload APIs > +
    • uevent support for hotplug This patch is removing all to replace it by Intel list. Instead of asking a new patch, I have applied and fixed it. From thomas at monjalon.net Thu Mar 8 23:31:23 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Thu, 08 Mar 2018 23:31:23 +0100 Subject: [dpdk-web] [PATCH 1/1] update 18.05 roadmap In-Reply-To: <1519406172-15580-2-git-send-email-erik.g.carrillo@intel.com> References: <1519406172-15580-1-git-send-email-erik.g.carrillo@intel.com> <1519406172-15580-2-git-send-email-erik.g.carrillo@intel.com> Message-ID: <16207875.IdmO2jH1Pe@xps> 23/02/2018 18:16, Erik Gabriel Carrillo: > Add the event timer adapter to 18.05 roadmap. > > Signed-off-by: Erik Gabriel Carrillo Applied, thanks From thomas at monjalon.net Thu Mar 8 23:34:51 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Thu, 08 Mar 2018 23:34:51 +0100 Subject: [dpdk-web] [PATCH] Remove ARM support for ark from roadmap In-Reply-To: References: <1520514449-4543-1-git-send-email-ed.czeck@atomicrules.com> Message-ID: <1971305.o901FBaCHS@xps> > > Signed-off-by: Ed Czeck > > Acked-by: John McNamara Applied, thanks From thomas at monjalon.net Thu Mar 8 23:47:08 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Thu, 08 Mar 2018 23:47:08 +0100 Subject: [dpdk-web] [RFC v3] Add LTS section on the roadmap page In-Reply-To: <20180306194354.19891-1-bluca@debian.org> References: <20180209130440.20380-1-bluca@debian.org> <20180306194354.19891-1-bluca@debian.org> Message-ID: <35393439.YGHAQigI8k@xps> 06/03/2018 20:43, Luca Boccassi: > Signed-off-by: Luca Boccassi Acked-by: Thomas Monjalon Applied, thanks From thomas at monjalon.net Fri Mar 9 14:36:12 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Fri, 9 Mar 2018 14:36:12 +0100 Subject: [dpdk-web] [PATCH] update stable releases roadmap Message-ID: <20180309133612.19927-1-thomas@monjalon.net> Signed-off-by: Thomas Monjalon --- This is at the same time, a call for volunteer, and a proposed change to shorten the wait for the first stable releases from at least 3 months to 2 months. Let's add this discussion to the agenda of the next techboard meeting. --- dev/roadmap.html | 35 +++++++++++++++++++++++++++++++---- 1 file changed, 31 insertions(+), 4 deletions(-) diff --git a/dev/roadmap.html b/dev/roadmap.html index e6cf640..e40f410 100644 --- a/dev/roadmap.html +++ b/dev/roadmap.html @@ -104,6 +104,8 @@
    • Release: November 2, 2018

    Stable releases

    +

    There is a documentation page describing the + guidelines of the stable releases.

    Stable point releases follow mainline releases.

    After each -rc tag and after the final version, relevant bug fixes get backported by the stable maintainers into the respective branches in "bursts". @@ -111,8 +113,9 @@ to stable at dpdk.org only (avoiding dev at dpdk.org).

    After all the relevant bugfixes have been backported, regression tests are ran, and if clear, the stable release is announced. -

    Typically a new stable release version follows a mainline release - by 1-2 weeks, depending on the test results. +

    The first stable release (.1) of a branch should follow + its mainline release (.0) by two months, + before starting tests of the next mainline release candidates.


    @@ -125,15 +128,39 @@ - + - + + + + + + + + + + + + + + + + + + + + + + + + +
    16.11.6 May 19, 2018November 2018November 2018 (LTS) Luca Boccassi
    17.11.2 May 19, 2018November 2019November 2019 (LTS) Yuanhan Liu
    18.02.1April 6, 2018June 2018looking for volunteer
    18.05.1June 29, 2018October 2018looking for volunteer
    18.08.1October 5, 2018January 2019looking for volunteer
    18.11.1January 11, 2019November 2020 (LTS)looking for volunteer
  • -- 2.16.2 From bluca at debian.org Fri Mar 9 14:44:51 2018 From: bluca at debian.org (Luca Boccassi) Date: Fri, 09 Mar 2018 13:44:51 +0000 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: <20180309133612.19927-1-thomas@monjalon.net> References: <20180309133612.19927-1-thomas@monjalon.net> Message-ID: <1520603091.5685.8.camel@debian.org> On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > Signed-off-by: Thomas Monjalon > > --- > This is at the same time, a call for volunteer, > and a proposed change to shorten the wait for the first stable > releases > from at least 3 months to 2 months. > > Let's add this discussion to the agenda of the next techboard > meeting. The issue is how to decide what goes into a stable release, if it does not follow a main release. Right now we follow the main release as that means there is a list of accepted and merged commits that can be backported - if the stable release is anticipated, what is going to be backported? -- Kind regards, Luca Boccassi From thomas at monjalon.net Fri Mar 9 14:49:27 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Fri, 09 Mar 2018 14:49:27 +0100 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: <1520603091.5685.8.camel@debian.org> References: <20180309133612.19927-1-thomas@monjalon.net> <1520603091.5685.8.camel@debian.org> Message-ID: <5601805.V4YcVmhU8q@xps> 09/03/2018 14:44, Luca Boccassi: > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > Signed-off-by: Thomas Monjalon > > > > --- > > This is at the same time, a call for volunteer, > > and a proposed change to shorten the wait for the first stable > > releases > > from at least 3 months to 2 months. > > > > Let's add this discussion to the agenda of the next techboard > > meeting. > > The issue is how to decide what goes into a stable release, if it does > not follow a main release. > > Right now we follow the main release as that means there is a list of > accepted and merged commits that can be backported - if the stable > release is anticipated, what is going to be backported? If we pull patches more regularly in master, there can be a lot of fixes accumulated during 2 months. From konstantin.ananyev at intel.com Fri Mar 9 15:03:59 2018 From: konstantin.ananyev at intel.com (Ananyev, Konstantin) Date: Fri, 9 Mar 2018 14:03:59 +0000 Subject: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap In-Reply-To: <5601805.V4YcVmhU8q@xps> References: <20180309133612.19927-1-thomas@monjalon.net> <1520603091.5685.8.camel@debian.org> <5601805.V4YcVmhU8q@xps> Message-ID: <2601191342CEEE43887BDE71AB97725890F22385@irsmsx105.ger.corp.intel.com> > -----Original Message----- > From: techboard [mailto:techboard-bounces at dpdk.org] On Behalf Of Thomas Monjalon > Sent: Friday, March 9, 2018 1:49 PM > To: Luca Boccassi > Cc: web at dpdk.org; yliu at fridaylinux.org; ktraynor at redhat.com; techboard at dpdk.org > Subject: Re: [dpdk-techboard] [dpdk-web] [PATCH] update stable releases roadmap > > 09/03/2018 14:44, Luca Boccassi: > > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > > Signed-off-by: Thomas Monjalon > > > > > > --- > > > This is at the same time, a call for volunteer, > > > and a proposed change to shorten the wait for the first stable > > > releases > > > from at least 3 months to 2 months. > > > > > > Let's add this discussion to the agenda of the next techboard > > > meeting. > > > > The issue is how to decide what goes into a stable release, if it does > > not follow a main release. > > > > Right now we follow the main release as that means there is a list of > > accepted and merged commits that can be backported - if the stable > > release is anticipated, what is going to be backported? > > If we pull patches more regularly in master, there can be a lot of fixes > accumulated during 2 months. But these patches need to be properly tested before going into LTS, right? So it means extra effort for the validation teams? Konstantin From thomas at monjalon.net Fri Mar 9 15:19:10 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Fri, 09 Mar 2018 15:19:10 +0100 Subject: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap In-Reply-To: <2601191342CEEE43887BDE71AB97725890F22385@irsmsx105.ger.corp.intel.com> References: <20180309133612.19927-1-thomas@monjalon.net> <5601805.V4YcVmhU8q@xps> <2601191342CEEE43887BDE71AB97725890F22385@irsmsx105.ger.corp.intel.com> Message-ID: <138268661.yuZPGn2xFY@xps> 09/03/2018 15:03, Ananyev, Konstantin: > From: Thomas Monjalon > > 09/03/2018 14:44, Luca Boccassi: > > > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > > > Signed-off-by: Thomas Monjalon > > > > > > > > --- > > > > This is at the same time, a call for volunteer, > > > > and a proposed change to shorten the wait for the first stable > > > > releases > > > > from at least 3 months to 2 months. > > > > > > > > Let's add this discussion to the agenda of the next techboard > > > > meeting. > > > > > > The issue is how to decide what goes into a stable release, if it does > > > not follow a main release. > > > > > > Right now we follow the main release as that means there is a list of > > > accepted and merged commits that can be backported - if the stable > > > release is anticipated, what is going to be backported? > > > > If we pull patches more regularly in master, there can be a lot of fixes > > accumulated during 2 months. > > But these patches need to be properly tested before going into LTS, right? > So it means extra effort for the validation teams? Exact The stable release must be validated anyway. The proposal is to validate the .1 release before starting RC1 validation, instead of doing it after the .0 release. From ktraynor at redhat.com Fri Mar 9 15:30:04 2018 From: ktraynor at redhat.com (Kevin Traynor) Date: Fri, 9 Mar 2018 14:30:04 +0000 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: <20180309133612.19927-1-thomas@monjalon.net> References: <20180309133612.19927-1-thomas@monjalon.net> Message-ID: hi Thomas, On 03/09/2018 01:36 PM, Thomas Monjalon wrote: > Signed-off-by: Thomas Monjalon > > --- > This is at the same time, a call for volunteer, > and a proposed change to shorten the wait for the first stable releases > from at least 3 months to 2 months. > > Let's add this discussion to the agenda of the next techboard meeting. > --- > dev/roadmap.html | 35 +++++++++++++++++++++++++++++++---- > 1 file changed, 31 insertions(+), 4 deletions(-) > > diff --git a/dev/roadmap.html b/dev/roadmap.html > index e6cf640..e40f410 100644 > --- a/dev/roadmap.html > +++ b/dev/roadmap.html > @@ -104,6 +104,8 @@ >
  • Release: November 2, 2018 > >

    Stable releases

    > +

    There is a documentation page describing the > + guidelines of the stable releases. >

    Stable point releases follow mainline releases. >

    After each -rc tag and after the final version, relevant bug fixes get > backported by the stable maintainers into the respective branches in "bursts". > @@ -111,8 +113,9 @@ > to stable at dpdk.org only (avoiding dev at dpdk.org). >

    After all the relevant bugfixes have been backported, > regression tests are ran, and if clear, the stable release is announced. > -

    Typically a new stable release version follows a mainline release > - by 1-2 weeks, depending on the test results. > +

    The first stable release (.1) of a branch should follow > + its mainline release (.0) by two months, > + before starting tests of the next mainline release candidates. >


    >
    > > @@ -125,15 +128,39 @@ > > > > - > + > > > > > > - > + > > > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + I am available to volunteer for 18.11 :-) thanks, Kevin. > + >
    16.11.6May 19, 2018November 2018November 2018 (LTS)Luca Boccassi
    17.11.2May 19, 2018November 2019November 2019 (LTS)Yuanhan Liu
    18.02.1April 6, 2018June 2018looking for volunteer
    18.05.1June 29, 2018October 2018looking for volunteer
    18.08.1October 5, 2018January 2019looking for volunteer
    18.11.1January 11, 2019November 2020 (LTS)looking for volunteer
    >
    > > From thomas at monjalon.net Fri Mar 9 15:51:18 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Fri, 09 Mar 2018 15:51:18 +0100 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: References: <20180309133612.19927-1-thomas@monjalon.net> Message-ID: <1693695.kNmLWgLox0@xps> Hi Kevin, 09/03/2018 15:30, Kevin Traynor: > hi Thomas, > > On 03/09/2018 01:36 PM, Thomas Monjalon wrote: > > + 18.11.1 > > + January 11, 2019 > > + November 2020 (LTS) > > + looking for volunteer > > I am available to volunteer for 18.11 :-) Thanks a lot, I will add your name when approved by the Technical Board. Any time available to experience stable releases with non-LTS 18.05.x during the summer? From ferruh.yigit at intel.com Fri Mar 9 16:24:01 2018 From: ferruh.yigit at intel.com (Ferruh Yigit) Date: Fri, 9 Mar 2018 15:24:01 +0000 Subject: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap In-Reply-To: <138268661.yuZPGn2xFY@xps> References: <20180309133612.19927-1-thomas@monjalon.net> <5601805.V4YcVmhU8q@xps> <2601191342CEEE43887BDE71AB97725890F22385@irsmsx105.ger.corp.intel.com> <138268661.yuZPGn2xFY@xps> Message-ID: On 3/9/2018 2:19 PM, Thomas Monjalon wrote: > 09/03/2018 15:03, Ananyev, Konstantin: >> From: Thomas Monjalon >>> 09/03/2018 14:44, Luca Boccassi: >>>> On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: >>>>> Signed-off-by: Thomas Monjalon >>>>> >>>>> --- >>>>> This is at the same time, a call for volunteer, >>>>> and a proposed change to shorten the wait for the first stable >>>>> releases >>>>> from at least 3 months to 2 months. >>>>> >>>>> Let's add this discussion to the agenda of the next techboard >>>>> meeting. >>>> >>>> The issue is how to decide what goes into a stable release, if it does >>>> not follow a main release. >>>> >>>> Right now we follow the main release as that means there is a list of >>>> accepted and merged commits that can be backported - if the stable >>>> release is anticipated, what is going to be backported? >>> >>> If we pull patches more regularly in master, there can be a lot of fixes >>> accumulated during 2 months. >> >> But these patches need to be properly tested before going into LTS, right? >> So it means extra effort for the validation teams? > > Exact > The stable release must be validated anyway. > The proposal is to validate the .1 release before starting RC1 validation, > instead of doing it after the .0 release. I have same concern with Konstantin. Why merging unverified patches to the stable tree? It is not uncommon that we fix fixes during rc phase. I am for waiting proper release to backport fixes to the stable release. For specific cases, like backporting a specific hot fixes to the stable, I understand having stable release before actual release, but for that case the scope and what to focus/test is limited and can be managed. Is there a request received to get stable trees earlier? What is the motivation of the change? From ktraynor at redhat.com Fri Mar 9 16:43:04 2018 From: ktraynor at redhat.com (Kevin Traynor) Date: Fri, 9 Mar 2018 15:43:04 +0000 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: <1693695.kNmLWgLox0@xps> References: <20180309133612.19927-1-thomas@monjalon.net> <1693695.kNmLWgLox0@xps> Message-ID: <182bd68a-4660-429b-b9f5-dd4987ba8da3@redhat.com> On 03/09/2018 02:51 PM, Thomas Monjalon wrote: > Hi Kevin, > > 09/03/2018 15:30, Kevin Traynor: >> hi Thomas, >> >> On 03/09/2018 01:36 PM, Thomas Monjalon wrote: >>> + 18.11.1 >>> + January 11, 2019 >>> + November 2020 (LTS) >>> + looking for volunteer >> >> I am available to volunteer for 18.11 :-) > > Thanks a lot, I will add your name when approved > by the Technical Board. > Sure, thanks > Any time available to experience stable releases > with non-LTS 18.05.x during the summer? > Sorry, I can't commit for it because lack of bandwidth between work and holidays > From thomas at monjalon.net Fri Mar 9 16:45:18 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Fri, 09 Mar 2018 16:45:18 +0100 Subject: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap In-Reply-To: References: <20180309133612.19927-1-thomas@monjalon.net> <138268661.yuZPGn2xFY@xps> Message-ID: <1763732.gKnBn278kB@xps> 09/03/2018 16:24, Ferruh Yigit: > On 3/9/2018 2:19 PM, Thomas Monjalon wrote: > > 09/03/2018 15:03, Ananyev, Konstantin: > >> From: Thomas Monjalon > >>> 09/03/2018 14:44, Luca Boccassi: > >>>> On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > >>>>> Signed-off-by: Thomas Monjalon > >>>>> > >>>>> --- > >>>>> This is at the same time, a call for volunteer, > >>>>> and a proposed change to shorten the wait for the first stable > >>>>> releases > >>>>> from at least 3 months to 2 months. > >>>>> > >>>>> Let's add this discussion to the agenda of the next techboard > >>>>> meeting. > >>>> > >>>> The issue is how to decide what goes into a stable release, if it does > >>>> not follow a main release. > >>>> > >>>> Right now we follow the main release as that means there is a list of > >>>> accepted and merged commits that can be backported - if the stable > >>>> release is anticipated, what is going to be backported? > >>> > >>> If we pull patches more regularly in master, there can be a lot of fixes > >>> accumulated during 2 months. > >> > >> But these patches need to be properly tested before going into LTS, right? > >> So it means extra effort for the validation teams? > > > > Exact > > The stable release must be validated anyway. > > The proposal is to validate the .1 release before starting RC1 validation, > > instead of doing it after the .0 release. > > I have same concern with Konstantin. > > Why merging unverified patches to the stable tree? It is not uncommon that we > fix fixes during rc phase. > > I am for waiting proper release to backport fixes to the stable release. It is a valid concern. > For specific cases, like backporting a specific hot fixes to the stable, I > understand having stable release before actual release, but for that case the > scope and what to focus/test is limited and can be managed. > > Is there a request received to get stable trees earlier? What is the motivation > of the change? When a bug is found just after a major release .0, we must wait the next major release to get it fixed in a release. I find it frustrating. My thought is that the stable branch should help between two major releases. If not releasing .1 between two major releases, we could at least update the branch more regularly. It is currently a burst 2 weeks before releasing the stable version, i.e. after the new major release which already contains all the new fixes. Some companies do not rely on the stable branches for the support of their customers because the patches are applied too late. It is a pity. It is OK that companies have their own backport with different risks and priorities considerations. But we should try to have a common community basis of backports without waiting 3 months. The other concern is how to spread the validation efforts of the main and stable releases over the year without overlaps. From bluca at debian.org Fri Mar 9 18:30:27 2018 From: bluca at debian.org (Luca Boccassi) Date: Fri, 09 Mar 2018 17:30:27 +0000 Subject: [dpdk-web] [dpdk-techboard] [PATCH] update stable releases roadmap In-Reply-To: <1763732.gKnBn278kB@xps> References: <20180309133612.19927-1-thomas@monjalon.net> <138268661.yuZPGn2xFY@xps> <1763732.gKnBn278kB@xps> Message-ID: <1520616627.5685.10.camel@debian.org> On Fri, 2018-03-09 at 16:45 +0100, Thomas Monjalon wrote: > 09/03/2018 16:24, Ferruh Yigit: > > On 3/9/2018 2:19 PM, Thomas Monjalon wrote: > > > 09/03/2018 15:03, Ananyev, Konstantin: > > > > From: Thomas Monjalon > > > > > 09/03/2018 14:44, Luca Boccassi: > > > > > > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > > > > > > Signed-off-by: Thomas Monjalon > > > > > > > > > > > > > > --- > > > > > > > This is at the same time, a call for volunteer, > > > > > > > and a proposed change to shorten the wait for the first > > > > > > > stable > > > > > > > releases > > > > > > > from at least 3 months to 2 months. > > > > > > > > > > > > > > Let's add this discussion to the agenda of the next > > > > > > > techboard > > > > > > > meeting. > > > > > > > > > > > > The issue is how to decide what goes into a stable release, > > > > > > if it does > > > > > > not follow a main release. > > > > > > > > > > > > Right now we follow the main release as that means there is > > > > > > a list of > > > > > > accepted and merged commits that can be backported - if the > > > > > > stable > > > > > > release is anticipated, what is going to be backported? > > > > > > > > > > If we pull patches more regularly in master, there can be a > > > > > lot of fixes > > > > > accumulated during 2 months. > > > > > > > > But these patches need to be properly tested before going into > > > > LTS, right? > > > > So it means extra effort for the validation teams? > > > > > > Exact > > > The stable release must be validated anyway. > > > The proposal is to validate the .1 release before starting RC1 > > > validation, > > > instead of doing it after the .0 release. > > > > I have same concern with Konstantin. > > > > Why merging unverified patches to the stable tree? It is not > > uncommon that we > > fix fixes during rc phase. > > > > I am for waiting proper release to backport fixes to the stable > > release. > > It is a valid concern. > > > For specific cases, like backporting a specific hot fixes to the > > stable, I > > understand having stable release before actual release, but for > > that case the > > scope and what to focus/test is limited and can be managed. > > > > Is there a request received to get stable trees earlier? What is > > the motivation > > of the change? > > When a bug is found just after a major release .0, we must wait the > next > major release to get it fixed in a release. I find it frustrating. > My thought is that the stable branch should help between two major > releases. > If not releasing .1 between two major releases, we could at least > update the branch more regularly. It is currently a burst 2 weeks > before releasing the stable version, i.e. after the new major release > which already contains all the new fixes. > > Some companies do not rely on the stable branches for the support of > their > customers because the patches are applied too late. It is a pity. > It is OK that companies have their own backport with different risks > and priorities considerations. But we should try to have a common > community basis of backports without waiting 3 months. > > The other concern is how to spread the validation efforts of the > main and stable releases over the year without overlaps. I am OK with doing more stable releases for 16.11 depending on specific bug fixes that are important enough - but I think it should be in addition to the releases that we do after a mainline release, and for specific and well-tested individual fixes, rather than for everything that was merged before RC1, as I believe it's too risky, for the same reasons that Ferruh mentioned. It should also be dependent on the companies providing regression tests (currently Intel and AT&T for 16.11) being available to commit the additional time, or for some other company to provide similar QA resources. -- Kind regards, Luca Boccassi From thomas at monjalon.net Thu Mar 15 23:33:22 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Thu, 15 Mar 2018 23:33:22 +0100 Subject: [dpdk-web] [dpdk-dev] [PATCH v2] Adding SUSE logo In-Reply-To: <20180315170503.28940-1-mvarlese@suse.de> References: <20180315170503.28940-1-mvarlese@suse.de> Message-ID: <2600077.xG3DTX1DJj@xps> 15/03/2018 18:05, mvarlese at suse.de: > From: Marco Varlese > > SUSE is among the companies packaging and distributing DPDK in > its open and enterprise distributions. > > Signed-off-by: Marco Varlese > --- > about/ecosystem.html | 1 + > logos/suse.png | Bin 0 -> 10824 bytes I have cropped the logo a bit to make it bigger on the page, and I moved the logo in alphabetical order in the middle of Linux distributions. Applied: http://dpdk.org/about/ecosystem PS: Cc web at dpdk.org which is the right mailing list From raychen at qiyi.com Mon Mar 19 07:56:56 2018 From: raychen at qiyi.com (Lei Chen) Date: Mon, 19 Mar 2018 14:56:56 +0800 Subject: [dpdk-web] [PATCH] add DPVS in the ecosystem Message-ID: <1521442616-18494-1-git-send-email-raychen@qiyi.com> Adding link to the DPVS (DPDK-LVS: a high performance Layer-4 load balancer based on DPDK) to the Ecosystem page. Signed-off-by: Lei Chen --- about/ecosystem.html | 1 + 1 file changed, 1 insertion(+) diff --git a/about/ecosystem.html b/about/ecosystem.html index f92ed79..6c2f53e 100644 --- a/about/ecosystem.html +++ b/about/ecosystem.html @@ -75,6 +75,7 @@
  • TRex
  • WARP17
  • YANFF +
  • DPVS

    Associate Members

    -- 2.7.4 From jiangwenjie at qiyi.com Mon Mar 19 04:07:06 2018 From: jiangwenjie at qiyi.com (=?gb2312?B?va/OxL3c?=) Date: Mon, 19 Mar 2018 03:07:06 +0000 Subject: [dpdk-web] Apply to add open source software DPVS to the DPDK ecosystem. Message-ID: <606231a529a648fb88c53cd0545f0335@EXCH09.iqiyi.pps> Hi, Thomas and helin I?m an IQIYI employee. On behalf of our team, I apply to add our open source software DPVS (https://github.com/iqiyi/dpvs ) to the DPDK ecosystem. The DPVS is a high performance Layer-4 load balancer based on DPDK and the attachment is its patch. Thank you very much! Regards, Wenjie From thomas at monjalon.net Mon Mar 19 21:19:06 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Mon, 19 Mar 2018 21:19:06 +0100 Subject: [dpdk-web] Apply to add open source software DPVS to the DPDK ecosystem. In-Reply-To: <606231a529a648fb88c53cd0545f0335@EXCH09.iqiyi.pps> References: <606231a529a648fb88c53cd0545f0335@EXCH09.iqiyi.pps> Message-ID: <1812200.ni1ul5FQQJ@xps> 19/03/2018 04:07, ???: > Hi, Thomas and helin > I?m an IQIYI employee. On behalf of our team, I apply to add our open source software DPVS (https://github.com/iqiyi/dpvs ) to the DPDK ecosystem. > The DPVS is a high performance Layer-4 load balancer based on DPDK and the attachment is its patch. Thank you very much! Added, in alphabetical order: http://dpdk.org/about/ecosystem Do not hesitate to participate in DPDK development, you will be welcome! From qiming.yang at intel.com Wed Mar 21 11:24:02 2018 From: qiming.yang at intel.com (Qiming Yang) Date: Wed, 21 Mar 2018 18:24:02 +0800 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs Message-ID: <20180321102402.78234-1-qiming.yang@intel.com> Signed-off-by: Qiming Yang --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@
  • e1000e (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)
  • igb (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)
  • ixgbe (82598, 82599, X520, X540, X550)
  • -
  • i40e (X710, XL710, X722)
  • +
  • i40e (X710, XL710, X722, XXV710)
  • fm10k (FM10420)
  • Note: The drivers e1000 and e1000e are also called em. -- 2.9.5 From qiming.yang at intel.com Wed Mar 21 15:25:10 2018 From: qiming.yang at intel.com (Qiming Yang) Date: Wed, 21 Mar 2018 22:25:10 +0800 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs Message-ID: <20180321142510.78518-1-qiming.yang@intel.com> Signed-off-by: Qiming Yang --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@

  • e1000e (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)
  • igb (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)
  • ixgbe (82598, 82599, X520, X540, X550)
  • -
  • i40e (X710, XL710, X722)
  • +
  • i40e (X710, XL710, X722, XXV710)
  • fm10k (FM10420)
  • Note: The drivers e1000 and e1000e are also called em. -- 2.9.5 From qiming.yang at intel.com Wed Mar 21 15:31:20 2018 From: qiming.yang at intel.com (Qiming Yang) Date: Wed, 21 Mar 2018 22:31:20 +0800 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs Message-ID: <20180321143120.78651-1-qiming.yang@intel.com> Signed-off-by: Qiming Yang --- doc/nics.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/nics.html b/doc/nics.html index ffe4455..58d6bf8 100644 --- a/doc/nics.html +++ b/doc/nics.html @@ -75,7 +75,7 @@

  • e1000e (82571, 82572, 82573, 82574, 82583, ICH8, ICH9, ICH10, PCH, PCH2, I217, I218, I219)
  • igb (82575, 82576, 82580, I210, I211, I350, I354, DH89xx)
  • ixgbe (82598, 82599, X520, X540, X550)
  • -
  • i40e (X710, XL710, X722)
  • +
  • i40e (X710, XL710, X722, XXV710)
  • fm10k (FM10420)
  • Note: The drivers e1000 and e1000e are also called em. -- 2.9.5 From thomas at monjalon.net Wed Mar 21 09:29:30 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Wed, 21 Mar 2018 09:29:30 +0100 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs In-Reply-To: <20180321143120.78651-1-qiming.yang@intel.com> References: <20180321143120.78651-1-qiming.yang@intel.com> Message-ID: <2016294.lWQek5x8rA@xps> 21/03/2018 15:31, Qiming Yang: > -

  • i40e (X710, XL710, X722)
  • > +
  • i40e (X710, XL710, X722, XXV710)
  • Please, could add in the message which release is supporting this device? From john.mcnamara at intel.com Wed Mar 21 10:14:38 2018 From: john.mcnamara at intel.com (Mcnamara, John) Date: Wed, 21 Mar 2018 09:14:38 +0000 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs In-Reply-To: <20180321143120.78651-1-qiming.yang@intel.com> References: <20180321143120.78651-1-qiming.yang@intel.com> Message-ID: > -----Original Message----- > From: web [mailto:web-bounces at dpdk.org] On Behalf Of Qiming Yang > Sent: Wednesday, March 21, 2018 2:31 PM > To: Yang, Qiming ; web at dpdk.org > Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs > > Signed-off-by: Qiming Yang Acked-by: John McNamara From john.mcnamara at intel.com Wed Mar 21 10:18:40 2018 From: john.mcnamara at intel.com (Mcnamara, John) Date: Wed, 21 Mar 2018 09:18:40 +0000 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs In-Reply-To: <2016294.lWQek5x8rA@xps> References: <20180321143120.78651-1-qiming.yang@intel.com> <2016294.lWQek5x8rA@xps> Message-ID: > -----Original Message----- > From: web [mailto:web-bounces at dpdk.org] On Behalf Of Thomas Monjalon > Sent: Wednesday, March 21, 2018 8:30 AM > To: Yang, Qiming > Cc: web at dpdk.org > Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs > > 21/03/2018 15:31, Qiming Yang: > > -
  • i40e > (X710, XL710, X722)
  • > > +
  • i40e > (X710, XL710, X722, XXV710)
  • > > Please, could add in the message which release is supporting this device? Just to clarify, you mean to add the release in the commit message not the html, right? John From thomas at monjalon.net Wed Mar 21 10:21:24 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Wed, 21 Mar 2018 10:21:24 +0100 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs In-Reply-To: References: <20180321143120.78651-1-qiming.yang@intel.com> <2016294.lWQek5x8rA@xps> Message-ID: <5636546.NRJykgjs9r@xps> 21/03/2018 10:18, Mcnamara, John: > > > -----Original Message----- > > From: web [mailto:web-bounces at dpdk.org] On Behalf Of Thomas Monjalon > > Sent: Wednesday, March 21, 2018 8:30 AM > > To: Yang, Qiming > > Cc: web at dpdk.org > > Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs > > > > 21/03/2018 15:31, Qiming Yang: > > > -
  • i40e > > (X710, XL710, X722)
  • > > > +
  • i40e > > (X710, XL710, X722, XXV710)
  • > > > > Please, could add in the message which release is supporting this device? > > > Just to clarify, you mean to add the release in the commit message not the html, right? Yes, just for the history, and for justification. From john.mcnamara at intel.com Wed Mar 21 10:26:16 2018 From: john.mcnamara at intel.com (Mcnamara, John) Date: Wed, 21 Mar 2018 09:26:16 +0000 Subject: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs In-Reply-To: <5636546.NRJykgjs9r@xps> References: <20180321143120.78651-1-qiming.yang@intel.com> <2016294.lWQek5x8rA@xps> <5636546.NRJykgjs9r@xps> Message-ID: > -----Original Message----- > From: Thomas Monjalon [mailto:thomas at monjalon.net] > Sent: Wednesday, March 21, 2018 9:21 AM > To: Mcnamara, John > Cc: Yang, Qiming ; web at dpdk.org > Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs > > 21/03/2018 10:18, Mcnamara, John: > > > > > -----Original Message----- > > > From: web [mailto:web-bounces at dpdk.org] On Behalf Of Thomas Monjalon > > > Sent: Wednesday, March 21, 2018 8:30 AM > > > To: Yang, Qiming > > > Cc: web at dpdk.org > > > Subject: Re: [dpdk-web] [PATCH] add XXV710 to i40e suppported NICs > > > > > > 21/03/2018 15:31, Qiming Yang: > > > > -
  • href="/doc/guides/nics/i40e.html">i40e > > > (X710, XL710, X722)
  • > > > > +
  • href="/doc/guides/nics/i40e.html">i40e > > > (X710, XL710, X722, XXV710)
  • > > > > > > Please, could add in the message which release is supporting this > device? > > > > > > Just to clarify, you mean to add the release in the commit message not > the html, right? > > Yes, just for the history, and for justification. Ok. Qiming, could you submit a V2 with a commit message that states when XXV710 support was added. From jiangwenjie at qiyi.com Tue Mar 20 02:25:57 2018 From: jiangwenjie at qiyi.com (=?utf-8?B?6JKL5paH5p2w?=) Date: Tue, 20 Mar 2018 01:25:57 +0000 Subject: [dpdk-web] =?utf-8?b?562U5aSNOiBBcHBseSB0byBhZGQgb3BlbiBzb3VyY2Ug?= =?utf-8?q?software_DPVS_to_the_DPDK_ecosystem=2E?= In-Reply-To: <1812200.ni1ul5FQQJ@xps> References: <606231a529a648fb88c53cd0545f0335@EXCH09.iqiyi.pps> <1812200.ni1ul5FQQJ@xps> Message-ID: Thank you Thomas ! Thank you Helin! -----????----- ???: Thomas Monjalon [mailto:thomas at monjalon.net] ????: 2018?3?20? 4:19 ???: ??? ??: helin.zhang at intel.com; web at dpdk.org ??: Re: Apply to add open source software DPVS to the DPDK ecosystem. 19/03/2018 04:07, ???: > Hi, Thomas and helin > I?m an IQIYI employee. On behalf of our team, I apply to add our open source software DPVS (https://github.com/iqiyi/dpvs ) to the DPDK ecosystem. > The DPVS is a high performance Layer-4 load balancer based on DPDK and the attachment is its patch. Thank you very much! Added, in alphabetical order: http://dpdk.org/about/ecosystem Do not hesitate to participate in DPDK development, you will be welcome! From bluca at debian.org Thu Mar 22 12:03:15 2018 From: bluca at debian.org (Luca Boccassi) Date: Thu, 22 Mar 2018 11:03:15 +0000 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: <20180309133612.19927-1-thomas@monjalon.net> References: <20180309133612.19927-1-thomas@monjalon.net> Message-ID: <1521716595.14111.56.camel@debian.org> On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > Signed-off-by: Thomas Monjalon > > --- > This is at the same time, a call for volunteer, > and a proposed change to shorten the wait for the first stable > releases > from at least 3 months to 2 months. > > Let's add this discussion to the agenda of the next techboard > meeting. > --- > ?dev/roadmap.html | 35 +++++++++++++++++++++++++++++++---- > ?1 file changed, 31 insertions(+), 4 deletions(-) > > diff --git a/dev/roadmap.html b/dev/roadmap.html > index e6cf640..e40f410 100644 > --- a/dev/roadmap.html > +++ b/dev/roadmap.html > @@ -104,6 +104,8 @@ > ?
  • Release: November 2, 2018 > ? > ?

    Stable releases

    > +

    There is a documentation page describing the > + guidelines of > the stable releases. > ?

    Stable point releases follow mainline releases. > ?

    After each -rc tag and after the final version, relevant > bug fixes get > ? backported by the stable maintainers into the respective > branches in "bursts". > @@ -111,8 +113,9 @@ > ? to stable at dpdk.org only (avoiding dev at dpdk.org). > ?

    After all the relevant bugfixes have been backported, > ? regression tests are ran, and if clear, the stable release > is announced. > -

    Typically a new stable release version follows a mainline > release > - by 1-2 weeks, depending on the test results. > +

    The first stable release (.1) of a branch should follow > + its mainline release (.0) by two months, > + before starting tests of the next mainline release > candidates. > ?


    > ?
    > ? > @@ -125,15 +128,39 @@ > ? > ? > ? > - > + > ? > ? > ? > ? > ? > - > + > ? > ? > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > + > ?
    16.11.6May 19, 2018November 2018November 2018 (LTS)Luca Boccassi
    17.11.2May 19, 2018November 2019November 2019 (LTS)Yuanhan Liu
    18.02.1April 6, 2018June 2018looking for volunteer
    18.05.1June 29, 2018October 2018looking for volunteer
    18.08.1October 5, 2018January 2019looking for volunteer
    18.11.1January 11, 2019November 2020 (LTS)looking for volunteer
    > ?
    > ? Hi, I'm happy to help with 18.02.1. Given it will be based on 18.05-rc2, which is due out on approximately April 20th, I think we can be ambitious and target April 27th as the tentative release date. Note that ATT won't be able to help with regression tests this time around. John, may we count on help from Intel to run the usual batch of regression tests between the 20th and the 27th? -- Kind regards, Luca Boccassi From bluca at debian.org Thu Mar 22 12:22:07 2018 From: bluca at debian.org (Luca Boccassi) Date: Thu, 22 Mar 2018 11:22:07 +0000 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: <1521716595.14111.56.camel@debian.org> References: <20180309133612.19927-1-thomas@monjalon.net> <1521716595.14111.56.camel@debian.org> Message-ID: <1521717727.14111.58.camel@debian.org> On Thu, 2018-03-22 at 11:03 +0000, Luca Boccassi wrote: > On Fri, 2018-03-09 at 14:36 +0100, Thomas Monjalon wrote: > > Signed-off-by: Thomas Monjalon > > > > --- > > This is at the same time, a call for volunteer, > > and a proposed change to shorten the wait for the first stable > > releases > > from at least 3 months to 2 months. > > > > Let's add this discussion to the agenda of the next techboard > > meeting. > > --- > > ?dev/roadmap.html | 35 +++++++++++++++++++++++++++++++---- > > ?1 file changed, 31 insertions(+), 4 deletions(-) > > > > diff --git a/dev/roadmap.html b/dev/roadmap.html > > index e6cf640..e40f410 100644 > > --- a/dev/roadmap.html > > +++ b/dev/roadmap.html > > @@ -104,6 +104,8 @@ > > ?
  • Release: November 2, 2018 > > ? > > ?

    Stable releases

    > > +

    There is a documentation page describing the > > + guidelines > > of > > the stable releases. > > ?

    Stable point releases follow mainline releases. > > ?

    After each -rc tag and after the final version, > > relevant > > bug fixes get > > ? backported by the stable maintainers into the respective > > branches in "bursts". > > @@ -111,8 +113,9 @@ > > ? to stable at dpdk.org only (avoiding dev at dpdk.org). > > ?

    After all the relevant bugfixes have been backported, > > ? regression tests are ran, and if clear, the stable release > > is announced. > > -

    Typically a new stable release version follows a > > mainline > > release > > - by 1-2 weeks, depending on the test results. > > +

    The first stable release (.1) of a branch should follow > > + its mainline release (.0) by two months, > > + before starting tests of the next mainline release > > candidates. > > ?


    > > ?
    > > ? > > @@ -125,15 +128,39 @@ > > ? > > ? > > ? > > - > > + > > ? > > ? > > ? > > ? > > ? > > - > > + > > ? > > ? > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > + > > ?
    16.11.6May 19, 2018November 2018November 2018 (LTS)Luca Boccassi
    17.11.2May 19, 2018November 2019November 2019 (LTS)Yuanhan Liu
    18.02.1April 6, 2018June 2018looking for volunteer
    18.05.1June 29, 2018October 2018looking for volunteer
    18.08.1October 5, 2018January 2019looking for volunteer
    18.11.1January 11, 2019November 2020 (LTS)looking for volunteer
    > > ?
    > > ? > > Hi, > > I'm happy to help with 18.02.1. > > Given it will be based on 18.05-rc2, which is due out on > approximately > April 20th, I think we can be ambitious and target April 27th as the > tentative release date. > > Note that ATT won't be able to help with regression tests this time > around. John, may we count on help from Intel to run the usual batch > of > regression tests between the 20th and the 27th? Slight misunderstanding, sorry - we'll want to base 18.02.1 on 18.05- rc1 (not rc2), which means the dates get pulled forward by 10 days - I'll make the branch available for review and eventually ask for help from backporters if needed on April the 10th, and ambitiously targeting release for April the 17th. So we'd need regression tests done before the 17th of April. -- Kind regards, Luca Boccassi From thomas at monjalon.net Thu Mar 22 12:25:12 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Thu, 22 Mar 2018 12:25:12 +0100 Subject: [dpdk-web] [PATCH] update stable releases roadmap In-Reply-To: <1521716595.14111.56.camel@debian.org> References: <20180309133612.19927-1-thomas@monjalon.net> <1521716595.14111.56.camel@debian.org> Message-ID: <101469652.poQfFCCKWp@xps> 22/03/2018 12:03, Luca Boccassi: > Hi, > > I'm happy to help with 18.02.1. Thanks a lot. For next stable branches, we must find more volunteers. > Given it will be based on 18.05-rc2, which is due out on approximately > April 20th, I think we can be ambitious and target April 27th as the > tentative release date. I think 18.02.1 should be based on 18.05-rc1, so April 20th would be a tentative release date for 18.02.1 (before 18.05-rc2). I will send a v2 of this schedule. > Note that ATT won't be able to help with regression tests this time > around. John, may we count on help from Intel to run the usual batch of > regression tests between the 20th and the 27th? Or one week before :) It would be good to have more companies involved in testing stable releases. We need to explicitly ask to some of the members. Can be done privately. From alialnu at mellanox.com Thu Mar 22 18:35:56 2018 From: alialnu at mellanox.com (Ali Alnubani) Date: Thu, 22 Mar 2018 18:35:56 +0100 Subject: [dpdk-web] [PATCH 1/5] add css styles for event pages Message-ID: <20180322173600.24189-1-alialnu@mellanox.com> Signed-off-by: Ali Alnubani Signed-off-by: Thomas Monjalon --- content.css | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/content.css b/content.css index 367549c..fea7dcc 100644 --- a/content.css +++ b/content.css @@ -68,6 +68,49 @@ section#news li em:first-child { display: block; } +section#event ul { + clear: left; + list-style: none; + margin-left: 0; +} +section#event li { + margin: 3em 0 1em 0; +} +section#event li > em { + display: inline-block; + margin-top: 1em; +} +section#event li > a { + float: right; + margin: 0.5em 0 0 2em; + vertical-align: top; + text-align: center; + text-decoration: none; +} +section#event li > a::after { + content: attr(class); +} +section#event li > a:hover::after { + text-decoration: underline; +} +section#event li > a .material-icons { + display: block; + font-size: 2em; +} +section#event li > a.Slides .material-icons::before { + content: "insert_drive_file"; +} +section#event li > a.Video .material-icons::before { + content: "play_circle_outline"; +} +section#event > img.venue { + float: left; + margin: 0 2em 2em 0; +} +section#event > img.room { + margin: 1em 0; +} + section pre { padding-left: 1em; border-left: solid 0.3em #782A90; -- 2.11.0 From alialnu at mellanox.com Thu Mar 22 18:35:58 2018 From: alialnu at mellanox.com (Ali Alnubani) Date: Thu, 22 Mar 2018 18:35:58 +0100 Subject: [dpdk-web] [PATCH 3/5] add Ireland's 2017 summit to archive In-Reply-To: <20180322173600.24189-1-alialnu@mellanox.com> References: <20180322173600.24189-1-alialnu@mellanox.com> Message-ID: <20180322173600.24189-3-alialnu@mellanox.com> Signed-off-by: Ali Alnubani Reviewed-by: Thomas Monjalon --- events.html | 2 +- events/summit-2017-ireland.html | 225 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 226 insertions(+), 1 deletion(-) create mode 100644 events/summit-2017-ireland.html diff --git a/events.html b/events.html index 8187ece..5d27e23 100644 --- a/events.html +++ b/events.html @@ -76,7 +76,7 @@

    › DPDK Userspace, Dublin - September 26-27, 2017

    - Archive | + Archive | Videos

    › DPDK Summit, Shanghai - June 27, 2017

    diff --git a/events/summit-2017-ireland.html b/events/summit-2017-ireland.html new file mode 100644 index 0000000..d02a410 --- /dev/null +++ b/events/summit-2017-ireland.html @@ -0,0 +1,225 @@ + + + + + + DPDK events + + + + + + + +
    +

    DPDK: Data Plane Development Kit

    + +
    +
    +

    DPDK Userspace, Dublin - September 26-27, 2017

    + +

    The two-day event was held at The Clayton Hotel in Dublin.

    + +
      +
    • +

      Tech Board Presentation & Panel Discussion

      +

      Presentation and panel session with the Technical Board on: Who the Tech Board are, what their responsibilities are, recent issues that they've addressed, future technical priorities/challenges.

      + Technical Board + + +
    • +
    • +

      Governing Board Presentation & Panel Discussion

      +

      Presentation and panel session with the Governing Board on: Who the Governing Board are, what their responsibilities are, progress to date, future priorities/challenges.

      + Governing Board + + +
    • +
    • +

      DPDK Bus Updates

      +

      DPDK bus infrastructure has been updated for last a few releases. Although these changes should not affect the user application, it worth mentioning the changes. In this talk, I will summarize the bus changes and mention from required modifications in drivers.

      + Ferruh Yigit (Intel) + + +
    • +
    • +

      Ideas for adding generic HW accelerators to DPDK

      +

      There are various kind of HW accelerators available with SoCs. Each of the accelerator may support different capabilities and interface. Many of these accelerators are programmable devices. In this talk we will discuss various ways to support such accelerators in a generic manner.

      + Hemant Agrawal (NXP) + + +
    • +
    • +

      Let?s hot plug: use uevent mechanism to practice it in DPDK

      +

      Hot plug is a key requirement for live migration. So far, the hot plug and fail-safe implementation is still not friendly for PCIe devices. This talk proposes to add a general uevent mechanism in DPDK which include the uevent monitor and failure handler, to make it easy for DPDK users to implement hot plug.

      + Jia Guo (Intel) + + +
    • +
    • +

      Proposed method for sharing a (PCI) device between multiple PMDs

      +

      Devices on the PCI bus are found by the bus probe function. For each device, the list of registered drivers (PMDs) is searched until one (only) is found for the device. This presentation proposes a mechanism to share a pci device between multiple PMDs. It may also be extendable to non-pci devices.

      + Fiona Trahe (Intel) + + +
    • +
    • +

      DPDK VMBus & Azure Support

      +

      This is talk about the current status and planned development of VMBus support for DPDK. This talk also gives an overview of how DPDK applications are enabled on Azure Accelerated Networking using the Fail-Safe, TAP and existing drivers. It will cover some of the requirements and plans for the future.

      + Stephen Hemminger (Microsoft) + + +
    • +
    • +

      rte_security: the case of IPsec offload

      +

      Encryption in today's networks is becoming ubiquitous. However, running crypto on general purpose CPUs is costly. In this talk we present joint work by NXP, Intel and Mellanox on offloading protocol processing to hardware providing better utilization of host CPU for packet processing.

      + Boris Pismenny (Mellanox), Declan Doherty (Intel), Hemant Agrawal (NXP) + + +
    • +
    • +

      DPDK Quality of Service APIs

      +

      This presentation focuses on the new QoS Traffic Management API for Ethernet devices that was introduced by DPDK release 17.08, as well as the new QoS Traffic Metering and Policing API planned for DPDK release 17.11. We describe the API, device drives currently supporting it and software fall-back strategy using the SoftNIC PMD.

      + Cristian Dumitrescu (Intel), Jasvinder Singh (Intel) + + +
    • +
    • +

      Service Cores: The path to Abstracting SW/HW CPU Requirements in DPDK

      +

      Service cores is a library that abstracts the platform, providing an app with a consistent environment. Service cores allows switching of SW and HW PMDs with no application threading changes. This talk introduces service-cores, and opens discussion on how to enable DPDK with service cores.

      + Harry van Haaren (Intel) + + +
    • +
    • +

      Wireless Base Band Device (bbdev)

      +

      Wireless Base Band Device (bbdev) proposal for DPDK that abstracts HW accelerators based on FPGA and/or Fixed Function Accelerators that assist with LTE Physical Layer processing. Furthermore, it decouples the application from the compute-intensive wireless functions by abstracting their optimized libraries to appear as virtual bbdev devices.

      + Amr Mokhtar (Intel) + + +
    • +
    • +

      DPDK to support InfiniBand Link Layer

      +

      There are many large InfiniBand clusters in the HPC market, they too would like to gain the DPDK user space high packet rate processing advantage, in addition to the RDMA capabilities. I will present the basic InfiniBand and IPoIB differences from Ethernet, and present results from a live POC on a 20 node cluster with DPDK using IPoIB

      + Shahaf Shuler (Mellanox) + + +
    • +
    • +

      Community Activity, CI & Tools

      +

      The userspace summit is a good place to make a yearly summary of community changes and interactions. It is also important to describe how DPDK interact with other communities. The last part would be about community processes (repositories, distributed CI, bugs tracking, tooling, website, mailing lists and Linux Foundation).

      + Thomas Monjalon (Mellanox), Qian Xu (Intel) + + +
    • +
    • +

      ABI Stability and LTS: Current state and Future

      +

      This session will be a panel discussion of the future direction of ABI stability & LTS/Stable releases. In particular it will look at the request for a yearly xx.11 LTS release with a 2 year duration.

      + John McNamara (Intel), Ian Stokes (Intel), Luca Boccassi (AT&T), Kevin Traynor (Red Hat) + + +
    • +
    • +

      Implementing an SR-IOV Hypervisor using DPDK

      +

      In the presentation we will describe VFd, a hypervisor for SRIOV NICs jointly developed by AT&T and Intel, which uses DPDK and acts as policy enforcement software allowing advanced configuration of SR-IOV capable Network Interfaces. We will provide overview of the use cases and new DPDK API?s to support them.

      + Alex Zelezniak (AT&T) + + +
    • +
    • +

      DPDK SRIOV and control over embedded switch

      +

      When working in SRIOV mode, we would prefer to let majority of the traffic to pass in HW directly from/to wire to/from VF, while the OVS-DPDK application only needs to handle exception packet flows on the PF. To support this mode we want to show a new Representor Ports model of the HW switch, which can be controlled from DPDK.

      + Alex Rosenbaum (Mellanox) + +
    • +
    • +

      A framework for representation, configuration, and management of virtual function ports in DPDK

      +

      This presentation introduces a port representor framework to DPDK. The framework based around a virtual representor PMD and representor broker plugin for physical function devices, provides the infrastructure to allow SR-IOV virtual function ports to be configured, managed and monitored within a single control application.

      + Declan Doherty (Intel) + + +
    • +
    • +

      Improve VNF safety with Vhost-User/DPDK IOMMU support

      +

      This talk will focus on improving VNF safety with Virtio and Vhost-user backend. Maxime will first describe VNF architecture relying on Virtio/Vhost-user. Then, he will talk about IOMMU support for the Vhost-user backend. Finally, Maxime will provide benchmarks results and discuss ways to improve both performance & safety.

      + Maxime Coquelin (Red Hat) + + +
    • +
    • +

      Virtio Status Update and New Ring Layout

      +

      The packed ring layout is the next generation ring layout standard for Virtio, which is designed for high performance and still in the proposal stage. This talk will give a quick introduction to this new ring layout definitions and summary the current status, findings and benchmark results of the prototype in DPDK.

      + Zhihong Wang (Intel) + + +
    • +
    • +

      Power Aware Packet Processing

      +

      A drive to deliver OPEX saving and performance where and when it's needed. Enter a new era of power optimized packet processing. This talk reviews new & existing dpdk extensions for policy based power control proposed in August and the associated performance benefits.

      + Chris MacNamara (Intel), Dave Hunt (Intel) + + +
    • +
    • +

      DPDK, VPP and pfSense 3.0

      +

      pfSense is a open source firewall/vpn appliance, based on FreeBSD, started in 2006 with over 1M active installs. We are basing pfSense release 3.0 on FD.io's VPP, leveraging key DPDK components including cryptodev, while adding a CLI and RESTCONF layer, leveraging FRRouting and Strongswan.

      + Jim Thompson (Netgate) + + +
    • +
    • +

      Rapid prototyping of DPDK applications with libmoon

      +

      This talk is about our framework libmoon, a wrapper for DPDK that makes building DPDK prototypes simple and fast. We've used it for multiple research prototypes as well as our packet generator MoonGen (presented last year here).

      + Paul Emmerich (Technical University of Munich) + + +
    • +
    • +

      Using DPDK with Go

      +

      In our presentation, we share the lesson learned from our experience using DPDK with Go in order to implement a software router Lagopus2 (https://github.com/lagopus/vsw). We'll explain how we carefully designed DPDK binding in Go to guarantee the type safeness and the performance at the same time.

      + Takanari Hayama (Igel) + + +
    • +
    • +

      T4P4S: When P4 meets DPDK

      +

      T4P4S is a P4 compiler supporting flexible re-targetability without sacrificing high performance packet processing. To achieve this goal, it is split into hardware dependent and independent components. This talk will show the architecture of T4P4S and the design decisions made to support DPDK.

      + S?ndor Laki (ELTE E?tv?s Lor?nd University) + + +
    • +
    • +

      Dataplane Networking journey in Containers

      +

      Our advanced Container Network Interface combines the benefits of containers with DPDK?s ultra-low latency and fast packet processing and the results show 28x more performance with SRIOV, DPDK using Vhost-User with OVS-DPDK and VPP.

      + Kuralamudhan Ramakrishnan (Intel), Gary Loughnane (Intel) + + +
    • +
    +
    +
    + + -- 2.11.0 From alialnu at mellanox.com Thu Mar 22 18:35:57 2018 From: alialnu at mellanox.com (Ali Alnubani) Date: Thu, 22 Mar 2018 18:35:57 +0100 Subject: [dpdk-web] [PATCH 2/5] add USA's 2017 summit to archive In-Reply-To: <20180322173600.24189-1-alialnu@mellanox.com> References: <20180322173600.24189-1-alialnu@mellanox.com> Message-ID: <20180322173600.24189-2-alialnu@mellanox.com> Signed-off-by: Ali Alnubani Reviewed-by: Thomas Monjalon --- events.html | 2 +- events/summit-2017-usa.html | 350 ++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 351 insertions(+), 1 deletion(-) create mode 100644 events/summit-2017-usa.html diff --git a/events.html b/events.html index 3ce2821..8187ece 100644 --- a/events.html +++ b/events.html @@ -69,7 +69,7 @@

    › DPDK Summit, San Jose - November 14-15, 2017

    - Archive | + Archive | Videos | Slides | Schedule diff --git a/events/summit-2017-usa.html b/events/summit-2017-usa.html new file mode 100644 index 0000000..14e87c4 --- /dev/null +++ b/events/summit-2017-usa.html @@ -0,0 +1,350 @@ + + + + + + DPDK events + + + + + + + +

    +

    DPDK: Data Plane Development Kit

    + +
    +
    +

    DPDK Summit, San Jose - November 14-15, 2017

    + +

    This event was held in Club Auto Sport, San Jose.

    + +
      +
    • +

      Opening Remarks & Governing Board

      +

      Introduction to the event, including a review of the agenda, logistics and expectations. An update from the Governing Board on who the Governing Board are, what their responsibilities are, progress to date, future priorities/challenges for the project.

      + Jim St. Leger (Intel) + + +
    • +
    • +

      Community Survey Feedback

      +

      We conducted a survey of the DPDK community, soliciting input on a variety of topics including DPDK usage, roadmap, performance, patch submission process, documentation and tools. This session will present the results of the survey, which will help to guide the future direction of the project.

      + John McNamara (Intel) + + +
    • +
    • +

      Reducing Barriers to Adoption - Making DPDK Easier to Integrate into Your Application

      +

      While DPDK is a widely-adopted software package for high-performance networking applications, there are a number of ways in which it is harder to use than it otherwise needs to be. This is especially true when it comes to integrating DPDK with an existing legacy codebase. This presentation will look at some of the issues and provide an update on current development and prototyping work to simplify DPDK integration with existing code.

      + Bruce Richardson (Intel) + + +
    • +
    • +

      New Command Line Interface for DPDK

      +

      The current command line interface for DPDK called cmdline has a number of limitation and a complex user design. The next command line for DPDK called CLI is more dynamic with a simple directory style design. The directory style design allows for commands to be placed in a hierarchy for easy integration, plus supporting a simple argc/argv function interface. Using these features reduced the LOC in test-pmd cmdline file from 12K to ~4K. The presentation includes an example usage.

      + Keith Wiles (Intel) + + +
    • +
    • +

      Event Adapters - Connecting Devices to Eventdev

      +

      Recently, the DPDK has enabled applications to use dynamically load balanced pipelines with the introduction of libeventdev. In addition to using eventdev for CPU to CPU pipelines, devices such as ethdev, cryptodev and timers need to be able to inject events into eventdev. Currently, we are in the process of upstreaming extensions to eventdev called eventdev adapters for each of these devices that would allow applications to configure event input from these devices to the event device. We will discuss each of the adapter APIs and show example code that allow event based applications to be written in a platform independent manner.

      + Nikhil Rao (Intel) + + +
    • +
    • +

      GRO/GSO Libraries: Bring Significant Performance Gains to DPDK-based Applications

      +

      A major part of packet processing has to be done on a per-packet basis, such as switching and TCP/IP header processing. The overhead of the per-packet routines, however, exerts a significant impact on the performance of network processing. Generic Receive Offload (GRO) and Generic Segmentation Offload (GSO) are two effective techniques for mitigating the per-packet processing overhead by reducing the number of packets to be processed. Specifically, GRO merges the receiving packets of the same flow in RX, while GSO delays packet segmentation in TX.

      + Jiayu Hu (Intel) + + +
    • +
    • +

      Power Aware Packet Processing

      +

      A drive to deliver OPEX saving and performance where and when it's needed. Enter a new era of power optimized packet processing. This talk reviews new & existing DPDK extensions for policy based power control proposed in August and the associated performance benefits.

      + Chris MacNamara (Intel) + + + + +
    • +
    • +

      Enhanced Memory Management

      +

      In this presentation we will be reviewing Enhanced Memory Management techniques and multi-process enhancements as a possible way to seamlessly solve burning issues like slow initialization, memory protection, memory hotplug, dynamic scale up/down, physically vs virtually contiguous, inter-vm shared memory etc.

      + Laszlo Vadkerti (Ericsson), Jiangtao Zhang (Ericsson) + + +
    • +
    • +

      Making networking apps scream on Windows with DPDK

      +

      Network bandwidth is precious and milliseconds matter for many user-mode applications and virtual appliances running on both Linux and Windows. In order to get the best network throughput to process and forward packets, developers need direct access to the NIC without going through the host networking stack. Until now, only developers on Linux and FreeBSD platforms were able to use DPDK to obtain these performance benefits but, we are happy to announce that we have an implementation of DPDK for the Windows platform!

      + Jason Messer (Microsoft), Manasi Deval (Intel) + + +
    • +
    • +

      Mediated Devices: Better Userland IO

      +

      Unbinding Linux kernel drivers to allow userland IO through VFIO has a number of disadvantages such as another large touchy code base to deal with the hardware, loss of standard Linux tools (ifconfig, ethtool, tcpdump, SNMPd...) and impossibility to accelerate container networking. Mediated device introduced in Linux kernel 4.10 for GPUs and provisions for additional devices hold the promise of collaboration between kernel drivers and userland application in need of direct datapath steering.

      + Fran?ois-Fr?d?ric Ozog (Linaro) + + +
    • +
    • +

      Mellanox bifurcated driver model

      +

      Mellanox PMD uses verbs instead of taking full control over the device (PCI). That allows the kernel (netdev) and more than a single PMD to run on a single PCI function. +If the DPDK app is not steering by rte_flow, all the traffic the packets be processed by the kernel net device.

      + Rony Efraim (Mellanox) + + +
    • +
    • +

      DPDK with KNI ? Pushing the Performance of an SDWAN Gateway to Highway Limits!

      +

      An SDWAN gateway is usually built with an x86 commercial off-the-shelf (COTS) hardware that often runs a variant of Linux Operating System and requires high throughput for connecting a corporate?s branch network with its Data Centers. However owing to the inherent limitations of standard 4K sized pages without dedicated resource allocations in a general-purpose Linux kernel, it has been seen that even a high-end SDWAN gateway hardware cannot forward traffic to its full potential.

      + Sabyasachi Sengupta (Nuage Networks) + + +
    • +
    • +

      DPDK as microservices in ZTE Paas

      +

      To provide high performance for ICT (Information Communications Technology) area, we use DPDK as a micro service in container networking. We used primary/secondary mode, rte_ring, sharing meory and so on, to promote the performance of datapath. We achieved bidirectional zero-copy between containers in contrast to only dequeue zero copy in vhost-user/virtio-user.

      + Yong Wang (ZTE), Songming Yan (ZTE) + + +
    • +
    • +

      Accelerate Clear Container Network performance

      +

      Clear Container is a great technology to secure a container with a fast and lightweight hypervisor, and there might be very different type of workloads running inside Clear Containers, e.g. some workloads require high packet processing rate (PPS) and some workloads require massive data transfer (BPS), given Clear Container?s much higher density than Virtual Machine, a high performance virtual switch is very critical and demands is highly emerged, but current available virtual switches is still far behind those demands.

      + Jun Xiao (CloudNetEngine) + + +
    • +
    • +

      The Path to Data Plane Microservices

      +

      DPDK revolutionized software packet processing initially for discrete appliances and then for Virtual Network Functions. Containers and ?Services technology are extensively used as a means to scale up and out in the Cloud. These technologies now include Comms Service Providers among their advocates, and embracing these technologies with their scaling model and resiliency is the new frontier in software packet processing.

      + Ray Kinsella (Intel) + + +
    • +
    • +

      Container Panel Discussion

      +

      A panel discussion with Yong Wang, Songming Yan, Jun Xiao and Ray Kinsella to discuss DPDK enablement of containers and micro-services.

      + +
    • +
    • +

      Accelerate storage service via SPDK

      +

      SPDK (storage performance development kit, http://spdk.io) is an open source library used to accelerate the storage service (e.g., file, block) especially for PCIe SSDs (e.g., 3D Xpoint SSDs). The foundation of SPDK is the user space, asynchronous and polled mode drivers (e.g., IOAT and NVMe), and the idea of which is similar to DPDK.

      + Jim Harris (Intel) + + +
    • +
    • +

      Accelerating P4-based Dataplane with DPDK

      +

      The high-level P4 programming language promises protocol and hardware-agnostic design of network functions. As the low-level functional implementation, the P4 Behavior Model (BMv2) provides the necessary constructional blocks (parser, deparser, lookup tables, and action primitives, etc.) into which any P4 dataplane programs can be compiled.

      + Peilong Li (University of Massachusetts Lowell) + + +
    • +
    • +

      Implementation and Testing of Soft Patch Panel

      +

      SPP is a framework to easily interconnect DPDK applications on host and guest virtual machines together, and assign resources dynamically to these applications. +As a carrier service provider, we expect that SPP improves performance and usability for inter-VM communication for large scale NFV environment.

      + Tetsuro Nakamura (NTT), Yasufumi Ogawa (NTT) + + +
    • +
    • +

      Reflections on Mirroring With DPDK

      +

      Debugging network problems is often hard, and further complicated when a guest O/S is provided with an SR-IOV VF bound to a DPDK driver because tools running on the physical host (e.g. tcpdump) lose visibility to the interface. Hardware mirroring of traffic to another VF provides the ability to regain visibility and to help facilitate the troubleshooting process.

      + E. Scott Daniels (AT&T Labs) + + +
    • +
    • +

      A network application API on top of device APIs

      +

      NFV promise is to be able to instantiate or even live migrate VMs on different platforms and have applications benefit from whatever acceleration is available. As a result, the application developer shall not make compilation or define application architecture based on what he/she expects from the runtime environment. ODP and DPDK have in common the concept of "device" APIs (Ethernet, crypto, events, IPsec, compression...) with distinct approaches.

      + Fran?ois-Fr?d?ric Ozog (Linaro) + + +
    • +
    • +

      SafetyOrange - a tiny server class multi-purpose box with DPDK

      +

      SafetyOrange is a portable (4.3 liter) and silent Xeon computer. Well, it is larger than 'DPDK in a box' but it supports two NICs (as of now sporting 2 XL710 cards), has 32G of memory and 14 cores. We have been using it for testing both native and virtualized DPDK appliances also whole virtual routers and served as a traffic generator for performance tests (DPDK pktgen), too. It is a brilliant development environment, too. And at the end of the day it still fits into a regular backpack.

      + Andras Kovacs (Ericsson), Laszlo Vadkerti (Ericsson) + + +
    • +
    • +

      Technical Roadmap

      +

      An update from the Technical Board covering the future roadmap and technical challenges for the project.

      + Technical Board + + +
    • +
    • +

      rte_raw_device: implementing programmable accelerators using generic offload

      +

      There are various kinds of HW accelerators available with SoCs. Each of the accelerators may support different capabilities and interfaces. Many of these accelerators are programmable devices. In this talk we will discuss the rte_raw_device and implementing a sample driver with it for NXP AIOP generic programmable accelerator.

      + Hemant Agrawal (NXP), Shreyansh Jain (NXP) + + +
    • +
    • +

      DPDK support for new hardware offloads

      +

      Fully programmable SmartNICs allow new offloads like OVS, eBPF, P4 or vRouter, and the Linux kernel is changing for supporting them. Having these same offloads when using DPDK is a possibility although the implications are not clear yet. We present Netronome?s perspective for adding such a support to DPDK mainly for OVS and eBPF.

      + Alejandro Lucero (Netronome) + + +
    • +
    • +

      Flexible and Extensible support for new protocol processing with DPDK using Dynamic Device Personalization

      +

      Dynamic Device Personalization allows a DPDK application to enable identification of new protocols, for example, GTP, PPPoE, QUIC, without changing the hardware. The demo showcases a DPDK application identifying and spreading traffic on GTP and QUIC. Dynamic Device Personalization can be used on any OS supported by DPDK, for example we showcase a QUIC protocol classification demo on Windows OS.

      + Andrey Chilikin (Intel), Brian Johnson (Intel) + + +
    • +
    • +

      Serverless DPDK - How SmartNIC resident DPDK Accelerates Packet Processing

      +

      Cloud architectures and business models are driving the need to ensure that all server compute resources have a revenue tie-in, heralding the march towards the serverless dataplane. This session presents a unique way to harness the power of DPDK to accelerate packet processing by pushing the data plane into a SmartNIC. We will discuss the motivation, benefits and challenges of implementing a DPDK based data plane running on the compute resources embedded in a SmartNIC.

      + Nishant Lodha (Cavium) + + +
    • +
    • +

      Enabling hardware acceleration in DPDK data plane applications

      +

      This presentation will look at the challenges faced in leveraging hardware acceleration in DPDK enabled applications, addressing some of the problems posed in creating consistent hardware agnostic APIs to support multiple accelerators with non-aligned features, and the knock implications this can have to application designs.

      + Declan Doherty (Intel) + + +
    • +
    • +

      rte_security: enhancing IPSEC offload

      +

      In this talk we present a joint work of NXP, Intel and Mellanox on offloading security protocol processing to hardware providing better utilization of host CPU for packet processing. This talk provides the overview of new enhancement in the rte_security APIs to support various features of IPSEC offloads as inline or lookaside offload.

      + Hemant Agrawal (NXP), Declan Doherty (Intel), Boris Pismenny (Mellanox) + + +
    • +
    • +

      Mellanox FPGA

      +

      The FPGA allows a wide variety of features to be supported in DPDK. +We observe that programmable HW is useful for packet-processing pipelines. +For example, consider a pipeline of multiple match-action operations, in which actions may also specify generic packet modifications that are carried out by accelerators. In this case, the CPU is only involved at the beginning (transmission) or end (reception) of the pipeline, while the accelerator invocations are initiated by NIC matching operations.

      + Boris Pismenny (Mellanox) + + +
    • +
    • +

      SMARTNIC, FPGA, IPSEC Panel discussion

      +

      A panel discussion with Hemant Agrawal, Alejandro Lucero, Andrey Chilikin, Brian Johnson, Nishant Lodha, Declan Doherty and Boris Pismenny to discuss DPDK enablement for smart NICs, FPGA and IPsec.

      + +
    • +
    • +

      VPP Host Stack

      +

      Although packet forwarding with VPP and DPDK can now scale to tens of millions of packets per second per core, lack of alternatives to kernel-based sockets means that containers and host applications cannot take full advantage of this speed. To fill this gap, VPP was recently added functionality specifically designed to allow containerized or host applications to communicate via shared-memory if co-located, or via a high-performance TCP stack inter-host.

      + Florin Coras (Cisco) + + +
    • +
    • +

      DPDK's best kept secret ? Micro-benchmark performance tests

      +

      To have apple to apple comparisons, developers need a common ground of base level metrics. That common ground is ability to identify the basic DPDK building block of importance (as well as relevance to the work load) e.g., producer/consumer rings and measure the cycle cost associated with basic operation like enque/dequeing ? bulk versus single.

      + Muthurajan Jayakumar (Intel) + + +
    • +
    • +

      DPDK on Microsoft Azure

      +

      SDN is at the foundation of all large scale networks in the public cloud, such as Microsoft Azure. But how do we make a software network scale to an era of 40/50+ gigabit networks and provide great performance for network applications and NFV in VMs? In this presentation, Daniel Firestone and Madhan Sivakumar will detail Azure Accelerated Networking for Linux with DPDK, using Azure's FPGA-based SmartNICs to accelerate Linux workloads using SR-IOV.

      + Daniel Firestone (Microsoft), Madhan Sivakumar (Microsoft) + + +
    • +
    • +

      OpenNetVM: A high-performance NFV platforms to meet future communication challenges

      +

      To truly achieve the vision of a high-performance software-based network that is flexible, lower-cost, and agile, a fast and carefully designed NFV platform along with a comprehensive SDN control plane is needed. Our high-performance NFV platform, OpenNetVM, exploits DPDK and enables high bandwidth network functions to operate at near line speed, while taking advantage of the flexibility and customization of low cost commodity servers.

      + K. K. Ramakrishnan (Univ. of California, Riverside) + + +
    • +
    • +

      Make DPDK's software traffic manager a deployable solution for vBNG

      +

      Achieving network functions parity across purpose-built ASIC implementation and virtual implementation is not straightforward. Irrespective of differences in performance capability between purpose-built and virtual environments. Functional disfiguration represents a significant obstacle in operators? adoption of virtualization as it implies a dependency on access/aggregation network topology and configuration.

      + Csaba Keszei (Ericsson) + + +
    • +
    • +

      OpenVswitch hardware offload over DPDK

      +

      Telcos and Cloud providers are looking for higher performance and scalability when building nextgen datacenters for NFV & SDN deployments. While running OVS over DPDK reduces the CPU overload of interrupt driven packet processing, CPU cores are still not completely freed up from polling of packet queues.

      + Rony Efraim (Mellanox) + + +
    • +
    • +

      Accelerating NFV with VMware's Enhanced Network Stack (ENS) and Intel's Poll Mode Drivers (PMD)

      +

      Network Functions Virtualization (NFV) deployments are happening at a rapid pace. This is driving the need to more efficiently consolidate compute, storage and communication workloads. NFV enables Communications Service Providers to migrate their fixed function networking elements to a general purpose server; however there is the need preserve the existing performance and latency. To support such workloads a vSwitch that enables both high throughput and low latency is a must.

      + Jin Heo (VMware), Rahul Shah (Intel) + + +
    • +
    • +

      DPDK Membership Library

      +

      In this talk we will present the new DPDK Membership Library, this library is used to create what we call a ?set-summary? which is a new data structure that is used to summarize large set of elements. It is the generalization and extension to the traditional filter structure, e.g. bloom filter, cuckoo filter, etc to efficiently test if a key belongs to a large set.

      + Sameh Gobriel (Intel) + + +
    • +
    • +

      Integrating and using DPDK with Open vSwitch

      +

      Some applications are written from the ground up with DPDK in mind, but Open vSwitch is not one of them. This talk will look at how Open vSwitch integrated and uses DPDK. It will look at various aspects such as DPDK initialization, threading, and the usage of DPDK PMD's and libraries. It will also talk about DPDK usability aspects such as LTS and API/ABI stability and the effect they have on Open vSwitch with DPDK.

      + Aaron Conole (Red Hat), Kevin Traynor (Red Hat) + + +
    • +
    • +

      Lagopus Router

      +

      In this talk, we introduce a new open source router implementation called Lagopus Router. It is an extensible microservice architecture router that consists of a DPDK router dataplane, router agents, and a pub/sub-based centralized configuration manager. These modules are written in Go and C and are loosely coupled to each other by gRPC.

      + Tomoya Hibi (NTT), Hirokazu Takahashi (NTT) + + +
    • +
    • +

      vSwitch Panel Discussion

      +

      A panel discussion with Rony Efraim, Jin Heo, Rahul Shah, Sameh Gobriel, Charlie Tai, Aaron Conole, Kevin Traynor, Tomoya Hibi and Hirokazu Takahashi to discuss DPDK acceleration of vswitches.

      + +
    • +
    • +

      Closing Remarks

      + Jim St. Leger (Intel) + +
    • +
    +
    +
    + + -- 2.11.0 From alialnu at mellanox.com Thu Mar 22 18:35:59 2018 From: alialnu at mellanox.com (Ali Alnubani) Date: Thu, 22 Mar 2018 18:35:59 +0100 Subject: [dpdk-web] [PATCH 4/5] add China's 2017 summit to archive In-Reply-To: <20180322173600.24189-1-alialnu@mellanox.com> References: <20180322173600.24189-1-alialnu@mellanox.com> Message-ID: <20180322173600.24189-4-alialnu@mellanox.com> Signed-off-by: Ali Alnubani Reviewed-by: Thomas Monjalon --- events.html | 2 +- events/summit-2017-china.html | 147 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 148 insertions(+), 1 deletion(-) create mode 100644 events/summit-2017-china.html diff --git a/events.html b/events.html index 5d27e23..d6ebc5e 100644 --- a/events.html +++ b/events.html @@ -81,7 +81,7 @@

    › DPDK Summit, Shanghai - June 27, 2017

    - Archive + Archive

    › DPDK Summit, Bangalore - April 25-26, 2017

    diff --git a/events/summit-2017-china.html b/events/summit-2017-china.html new file mode 100644 index 0000000..94ced78 --- /dev/null +++ b/events/summit-2017-china.html @@ -0,0 +1,147 @@ + + + + + + DPDK events + + + + + + + +

    +

    DPDK: Data Plane Development Kit

    + +
    +
    +

    DPDK Summit, Shanghai - June 27, 2017

    + +

    The event was held in Shanghai Marriott Hotel Hongqiao.

    + +
      +
    • +

      Opening

      +

      This presentation discussed the DPDK community and ecosystem status in China and worldwide, key direction, and event agenda.

      + Heqing Zhu (Intel) + +
    • +
    • +

      DPDK in Container: Status Quo and Future Directions

      +

      This presentation discussed how DPDK can accelerate the container networking, problems in both data and control planes, progress and plan.

      + Jianfeng Tan (Intel) + +
    • +
    • +

      F-Stack, a Full User Space Network Service on DPDK

      +

      This presentation discussed the F-Stack, its design principle, architecture, main components, performance, and development history in Tencent.

      + Hailong Wang (Tencent) + +
    • +
    • +

      A Better Virtio towards NFV Cloud

      +

      This presentation discussed the vHost data path acceleration technology to pave the way for Network Function Cloudification, including the roadmap to intercept DPDK, and the QEMU community.

      + Cunming Liang (Intel), Xiao Wang (Intel) + +
    • +
    • +

      Accelerate VM I/O via SPDK and Crypto for Generic vHost

      +

      This presentation discussed using DPDK generic vHost user library to build storage (vHost-SCSI) and crypto (vhost-crypto) applications.

      + Changpeng Liu (Intel), Xin Zeng (Intel) + +
    • +
    • +

      OVS-DPDK Practices in Meituan Cloud

      +

      This presentation discussed the OVS-DPDK trial in Meituan, its progress and challenges for large adoption, as well as the gaps and solutions.

      + Huai Huang (Meituan) + +
    • +
    • +

      Network Performance Tuning, Lesson Learned

      +

      This presentation discussed the performance optimization methods, key lessons, success story with Intel and DPDK technology to achieve the significant performance boost for wireless workload.

      + Fangliang Lou (ZTE) + +
    • +
    • +

      OPDL: on the Path to Packet Processing Nirvana

      +

      This presentation discussed an optimized packet distributor for core to core. OPDL decentralizes the distributor, all packets are maintained in order and atomic. It well addresses the high volume distribution needs for small packets.

      + Liang Ma (Intel) + +
    • +
    • +

      Intel? 25GbE Ethernet Adapter Advanced Features for NFV

      +

      This presentation discussed the new 25Gbe Ethernet feature in DPDK, how to transit from 10Gbe to 25Gbe using Intel Ethernet, device personalization, NFV use case such as VF Daemon and the Adaptive VF Guest Interface.

      + Helin Zhang (Intel), Jingjing Wu (Intel) + +
    • +
    • +

      Accelerate VPP Workload with DPDK Cryptodev Framework

      +

      This presentation discussed Cryptodev in DPDK framework and how to use it in VPP/IPsec scenario, as well as performance metric when Intel QAT is applied.

      + Fan Zhang (Intel) + +
    • +
    • +

      Data Center Security Use Case with DPDK

      +

      This presentation discussed Tencent cloud data center's security needs, why move from the dedicated chip to x86/DPDK paths, how to use the multiple process model to design the security service, which lead to thousands of server adoption.

      + Haohao Zhang (Tencent) + +
    • +
    • +

      Towards Low Latency Interrupt Mode PMD

      +

      This presentation discussed the interrupt/poll switching challenge, cost analysis to the interrupt PMD in baremtal and virutalization, as well as the tuning proposal of latency reduction.

      + Yunhong Jiang (Intel), Wei Wang (Intel) + +
    • +
    • +

      Telco Data Plane Status, Challenges and Solutions

      +

      This presentation discussed the evolved path on how to develop the network appliance in multiple generations, from kernel to user space, from MIPS to x86, from integrated to distributed model. In addition, this presentation discussed how to construct NFV system on dual-socket server.

      + Hao Lin (T1Networks) + +
    • +
    • +

      Support Millions Users in vBRAS

      +

      This presentation discussed the vBRAS on x86 platform and how to achieve millions of users' support.

      + Zhaohui Sun (Panabit) + +
    • +
    • +

      A High Speed DPDK PMD Approach in LXC

      +

      This presentation discussed a new PMD for container network optimization to connect Linux and DPDK, in addition to a new design based on the vectorized ring buffer.

      + Jie Zheng (United Stack) + +
    • +
    • +

      Cloud Data Center, Network Security Practices

      +

      This presentation discussed traffic monitoring and analysis, network visualization framework on DPDK, and how to construct an efficient security cloud.

      + Kai Wang (Yunshan) + +
    • +
    +
    +
    + + -- 2.11.0 From alialnu at mellanox.com Thu Mar 22 18:36:00 2018 From: alialnu at mellanox.com (Ali Alnubani) Date: Thu, 22 Mar 2018 18:36:00 +0100 Subject: [dpdk-web] [PATCH 5/5] add India's 2017 summit to archive In-Reply-To: <20180322173600.24189-1-alialnu@mellanox.com> References: <20180322173600.24189-1-alialnu@mellanox.com> Message-ID: <20180322173600.24189-5-alialnu@mellanox.com> Signed-off-by: Ali Alnubani Reviewed-by: Thomas Monjalon --- events.html | 2 +- events/summit-2017-india.html | 162 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 163 insertions(+), 1 deletion(-) create mode 100644 events/summit-2017-india.html diff --git a/events.html b/events.html index d6ebc5e..f004049 100644 --- a/events.html +++ b/events.html @@ -85,7 +85,7 @@

    › DPDK Summit, Bangalore - April 25-26, 2017

    - Archive | + Archive | Videos

    › DPDK Userspace, Dublin - October 20-21, 2016

    diff --git a/events/summit-2017-india.html b/events/summit-2017-india.html new file mode 100644 index 0000000..1867eb4 --- /dev/null +++ b/events/summit-2017-india.html @@ -0,0 +1,162 @@ + + + + + + DPDK events + + + + + + + +
    +

    DPDK: Data Plane Development Kit

    + +
    +
    +

    DPDK Summit, Bangalore - April 25-26, 2017

    + +

    The event was held in the Vivanta by Taj Hotel, Bangalore.

    + +
      +
    • +

      Introductions, Welcome and Agenda for the Day

      + Sujata Tibrewala (Intel) + + +
    • +
    • +

      DPDK Architecture and Roadmap

      +

      This talk will explore the motivation behind the existence of DPDK, why and how it evolved into what it is today and how the future roadmap addresses the needs of the Industry

      + Kannan Babu Ramia (Intel), Deepak K Jain (Intel) + + +
    • +
    • +

      Supporting SoC devices in DPDK - Status Update

      +

      This talk is an extension of a talk presented in DPDK Summit Userspace 2016 in Dublin, where NXP presented a case for expanding DPDK towards non-standard (SoC) devices. That required a large number of fundamental changes in the DPDK framework to untangle from PCI specific code/functionality. In this talk we delve into current upstream design of 1) the bus 'driver', 2) the mempool 'driver', 3) the device driver, and how these layers tie up together to provide the device model in DPDK framework.

      + Shreyansh Jain (NXP) + + +
    • +
    • +

      DPDK on an Intelligent NIC

      +

      This presentation is about using DPDK as firmware on an Intelligent NIC (OCTEON TX). It will cover the firmware architecture and how DPDK fits in that architecture. It will discuss the hurdles faced and solutions used as part of this exercise.

      + Vamsi Attunuru (Cavium) + + +
    • +
    • +

      Migrating from 10G to 25G

      +

      The Ethernet speed upgrade path was clearly defined as 10G->40G->100G. However, new developments in data center indicate the latest path for server connections will be 10G->25G->100G with potential for 10G->25G->50G->100G. This is because 25G provides a more efficient use of hardware and a more logical upgrade path to 100G.

      + Jingjing Wu (Intel), Helin Zhang (Intel) + + +
    • +
    • +

      DPDK Cook Book

      +

      The short talk is a quick tour of the book and show and tell of what each chapter contains. It is not going over the contents but giving info to developers as what each chapter contains.

      + Muthurajan Jaya Kumar (Intel) + + +
    • +
    • +

      Implementation of Flow-Based QoS Mechanism with OVS and DPDK

      +

      The project objective is to implement 'Flow based QoS' for SDN-NFV platform using OVS and DPDK on Intel architecture. We will apply this QoS mechanism on Wipro vCPE platform and demonstrate performance improvement of real time traffic.

      + Karuppusamy M (Wipro) + + +
    • +
    • +

      Fast Path Programming

      +

      This session is a primer on the prominence of P4 as a high-level, domain-specific language for data path applications. While there are a few ASIC vendors like Barefoot Networks who are coming up with compilers for their platforms, we are looking at expanding the reach of P4 for virtual infrastructure / software based data path by showcasing how P4 can become a choice for writing DPDK applications and thus enhanced portability.

      + Ramachandran Subramoniam (Happiest Minds), Vnpraveen Desu (Happiest Minds) + + +
    • +
    • +

      Dataplane for Subscriber Gateways

      +

      Subscriber gateways, such as BNG nodes, have unique requirements and challenges as compared to traditional routers. They need to be feature rich while also supporting high scale and throughput. This talk will provide an overview of a typical dataplane for subscriber gateways and highlight some of the design challenges in realizing the goals and the trade-offs to be considered.

      + Natarajan Venkataraman (Ericsson) + + +
    • +
    • +

      Sample VNF in OPNFV

      +

      The topic begins with an introduction for developing data plane feature rich Virtual Network Function (VNF) using optimized DPDK libraries including ip-pipeline packet framework and taking advantage of basic x86 architecture. It covers concept of developing data plane applications for running with RTC (Run To completion) mode or Pipeline mode with just configuration change. It also covers the generic Best Known Methods for developing optimized data plane application on x86 architecture with specific code examples from samplevnf project from OPNFV. Finally concludes with the call for action to community to contribute in the samplevnf project in OPNFV for application development.

      + Ramia Kannan Babu (Intel) + + +
    • +
    • +

      Fast Data IO / Vector Packet Processor: Architecture overview

      +

      FD.io (Fast Data) is architected as a collection of sub-projects and provides a modular, extensible user space IO services framework that supports rapid development of high-throughput, low-latency and resource-efficient IO services. At the heart of fd.io is Vector Packet Processing (VPP) technology. This session will give an overview of VPP, its architecture and how it pushes packet processing to extreme limits of performance and scale.

      + Shwetha Bhandari (Cisco) + + +
    • +
    • +

      Transport Layer Development Kit (TLDK)

      +

      This presentation provides an overview of the Transport Layer Development Kit (TLDK) project in FD.io.

      + Mohammad Abdul Awal (Intel) + + +
    • +
    • +

      SFC with OVS-DPDK and FD.io-DPDK

      +

      DPDK has become the ubiquitous user space framework on which prominent open source switching software, Open vSwitch and FD.io run, and is widely integrated in OPNFV. This session discusses Open DayLIght (ODL) based SFC on both OVS-DPDK and FD.io with DPDK, and provides a comparative study on architecture, performance and latency of SFC use case on ARM SoCs.

      + Prasad Gorja (NXP) + + +
    • +
    • +

      DPDK Automation in Red Hat OpenStack Platform

      +

      In this talk, we would like to take you through the Red Hat's effort to provision the OpenStack cluster with OVS-DPDK/SR-IOV datapath with the needed EPA parameters. We will describe the deployment steps, and the need for composable roles to handle today's VNF deployment scenarios.

      + Saravanan KR (Red Hat) + + +
    • +
    • +

      Packet Steering for Multicore Virtual Network Applications over DPDK

      +

      This presentation addresses the question of how packets must be steered from the kernel bypass mechanism to the user space applications. We investigate the following two questions: (i) Should packets be distributed to cores in hardware or in software? (ii) What information in the packet should be used to partition packets to cores?

      + Priyanka Naik (IIT Mumbai), Mitali Yadav (IIT Mumbai) + + +
    • +
    • +

      Cryptodev API

      +

      This presentation describes the cryptodev API, a framework for processing crypto workloads in DPDK. The cryptodev framework provides crypto poll mode drivers as well as a standard API that supports all these PMDs and can be used to perform various cipher, authentication, and AEAD symmetric crypto operations in DPDK. The library also provides the ability for effortless migration between hardware and software crypto accelerators.

      + Deepak K Jain (Intel) + + +
    • +
    +
    +
    + + -- 2.11.0 From thomas at monjalon.net Mon Mar 26 14:37:58 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Mon, 26 Mar 2018 14:37:58 +0200 Subject: [dpdk-web] [PATCH] update techboard minutes Message-ID: <20180326123758.4144-1-thomas@monjalon.net> Signed-off-by: Thomas Monjalon --- dev/techboard-minutes.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/dev/techboard-minutes.html b/dev/techboard-minutes.html index 8350348..8582031 100644 --- a/dev/techboard-minutes.html +++ b/dev/techboard-minutes.html @@ -50,6 +50,8 @@ sends minutes of its meetings on the mailing list. They are listed below.
      +
    • 2018-03-14 +
    • 2018-02-28
    • 2018-02-14
    • 2018-01-31
    • 2018-01-17 -- 2.16.2 From thomas at monjalon.net Mon Mar 26 15:39:16 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Mon, 26 Mar 2018 15:39:16 +0200 Subject: [dpdk-web] [PATCH 1/5] add css styles for event pages In-Reply-To: <20180322173600.24189-1-alialnu@mellanox.com> References: <20180322173600.24189-1-alialnu@mellanox.com> Message-ID: <12006607.9WTHay9Ta5@xps> 22/03/2018 18:35, Ali Alnubani: > Signed-off-by: Ali Alnubani > Signed-off-by: Thomas Monjalon Thank you Ali. The archives for 2017 events are now online: http://dpdk.org/events/summit-2017-india.html http://dpdk.org/events/summit-2017-china.html http://dpdk.org/events/summit-2017-ireland.html http://dpdk.org/events/summit-2017-usa.html Let's continue the migration of dpdksummit.com to dpdk.org with the latest India event and the older years. From yulong.pei at intel.com Mon Mar 26 08:07:07 2018 From: yulong.pei at intel.com (Yulong Pei) Date: Mon, 26 Mar 2018 14:07:07 +0800 Subject: [dpdk-web] [PATCH v1] add 18.02 Intel performance reports Message-ID: <1522044427-28022-1-git-send-email-yulong.pei@intel.com> Signed-off-by: Yulong Pei --- doc.html | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc.html b/doc.html index 007c807..f8a6ab6 100644 --- a/doc.html +++ b/doc.html @@ -71,6 +71,8 @@

    Performance Reports

      +
    • DPDK 18.02 Intel NIC Performance Report +
    • DPDK 18.02 Intel Vhost/Virtio Performance Report
    • DPDK 17.11 Intel NIC Performance Report
    • DPDK 17.11 Intel Vhost/Virtio Performance Report
    • DPDK 17.11 Intel Crypto Performance Report -- 2.5.0 From thomas at monjalon.net Tue Mar 27 17:21:30 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Tue, 27 Mar 2018 17:21:30 +0200 Subject: [dpdk-web] [PATCH v1] add 18.02 Intel performance reports In-Reply-To: <1522044427-28022-1-git-send-email-yulong.pei@intel.com> References: <1522044427-28022-1-git-send-email-yulong.pei@intel.com> Message-ID: <2247178.avnLLZG3Iy@xps> 26/03/2018 08:07, Yulong Pei: > Signed-off-by: Yulong Pei > --- > doc.html | 2 ++ Applied, thanks From raychen at qiyi.com Fri Mar 30 05:33:59 2018 From: raychen at qiyi.com (Lei Chen) Date: Fri, 30 Mar 2018 11:33:59 +0800 Subject: [dpdk-web] [PATCH] add DPVS logo in the ecosystem Message-ID: <1522380839-10202-1-git-send-email-raychen@qiyi.com> Replace text link to PNG logo link for DPVS, a high performance Layer-4 load balancer based on DPDK. Signed-off-by: Lei Chen --- about/ecosystem.html | 2 +- logos/dpvs.png | Bin 0 -> 8751 bytes 2 files changed, 1 insertion(+), 1 deletion(-) create mode 100644 logos/dpvs.png diff --git a/about/ecosystem.html b/about/ecosystem.html index 9085b94..8015f09 100644 --- a/about/ecosystem.html +++ b/about/ecosystem.html @@ -61,7 +61,7 @@
    • ANS
    • BESS
    • Butterfly -
    • DPVS +
    • DPVS
    • fd.io
    • Lagopus
    • MoonGen diff --git a/logos/dpvs.png b/logos/dpvs.png new file mode 100644 index 0000000000000000000000000000000000000000..61ea5d0898ea5ee90da7cc1dc163c1b34786a430 GIT binary patch literal 8751 zcmV+~BGBE5P)eI4itt=_FLVIF zP8LAQs9FO90|NtJlB*!qIDiq2+i5}&ZNdy00|NsCgN at K^NVO&$K{05`kgI`#fq^dS zkg*7WNDaT5=A6$4nq0-6Y65z=f9rv94;vU57Uz%ST z&Uwb8g*#TG0;;$+aL(gCoSRVqV@~>wa~@NmNTcFI>D?RssbR9XAmlG`r^;GE0LOmohM zeKt1}08Tjk`Y9R41Y^vrOp&#i5G0$_np_7j92*uE!GMn^`^3e=XQPHLl}%oqP>LK+ z>PWN!CD*maP6|MRy8Xpso&kX;jdRX?G&jQlF1xryH>HP1sMI+0+bYbVxP_T;^1dO- z#2OP8=zz~BxDA7P5evwB3#D=oy341>hur3}Y-Vj1uq3RS at er_;Y`CEle;|{R>T30AFncz&XZPMkA7) zZlIwxB--C*j8V8 at BZSZ9C%3Shv6~=RAHu at 3^%DHCZB!!JwAiQij$8*X9E-#KK87yH znu<*Z71ZoGp`^TCRA(Eo{YQk7jk~-K<-GOPeh(>zWt$&%mEsMgstzV~nM0 zQL*IYI(Xq&La=;LU>h!}8&(4;sTYJ5ZlE3~g at NNV5}k4n*DuP|jY~L5pjMxQ|GipA zgo+(jMy|pYd?H{I*tmoZHo^(9$VW_5cw*q#P6$@0upHrY=&o8LaPEf9IgOqb_q7AY z4Fh7_MWvH#*&b`qV3ce9Xhf1364tC`#;1P>mQua?AgIZWYE3w7lVQ=uLjfFjT`0PV zqteJ#q}v41H8yqe at YzP((=z1he6mfNh+ at wO)`^#i(m2u9HC&cM>J&)__Z$}O+ZFJ! zm#pL>c1^CLKtw8_4QO1#&Jb?!_djO{))S042y$waeOEVWN8|NY&T1fHEg99f1UXSC z*ChO($Ew1rZ8R0p=r9E94NlhSo^2FzRTjupw#VAlK;v#;Z9BOlS5YhYNI)Aad-3qu zGz<*f5v(Qo9%kFZ1sMoM7U-ZRF$SGJ+jKo8D1~|pswZ)yGUT{!hRI9Uz zJZxIwCZr at s5r<6^->M?&bPwBv5)T(Xgo1uzcaaR8$L_HoWxr4N8^ z at jH(KI4!;_8`sBOv&%*gvUOtiTfJZGALg99>IY#-mk2*1J{HtfhAHjGSdvcMp(5^S z2`V`3p_&_GjMZ8bHVrxt+^|lDxfuUWOAFSOej^MES?M<8sI$Jb=zDw3m>9;5!vSRQ z*NB+wwxh!R;-K?MUsC|*;Hw1`uH^v^@YO=`=Y;}zo at 4aT{b&v~Ra<;)@%Qx8dmb|i z_vQ%}16 at kiA(_SUMF at QiYPL2`bI!*kyn{_-D2&QHfu`(GYfBK2rNB6Uv=(v at q(HTv zjmtictLIgixv z9BxmExoIuX>G(O9gtxEOC}GNZUsBBgqKb|jr1rw*IOpNI$<*9WF>k1x(q$DL5LFB#nZalvHFA>W_+;vMPyHjK8#md1=)}uA&l?w(elQlE>=o5>{uI zP*_ at Zbd69`2-~-IQ!l6|06cem<_teRb0&3s=8Rcj^OmH-LaJGSyUylmW{t8u~8kVSGj6Q3gx8ASMsi|wP{nk?8iM4 zaP>m9uw*=5>|>G$whMILAF9Y~EplZA!JZ<%Y^?+nv|e&5T4ZFJgR6M?o0K&z&nmRA|QOHR?r%L+xeAxC=QV`+Y5}X4ucEM=mva5yu#&ZI0tUW zU%LnlR;mTu)~vl}K^tUME4li9-_>Ou;i-B~zacgtGP;dH&beLhX+Y&@Ry>Ivqp-A! z{K7SIwOWpSef=t4MXQC37?k5gH&^8t+_~GTT{8)TYW+Xt!99IVuBhN;>EF8>y9f5* z&A;;&G_epytPwPan$Q>S#fSdr3D~ynRJBF|Jl|cTR&w>!C0tlqMSgx+>OEAsgkfqH z*P~vvdLG7D0<=|Vh8SZJ7uGS=;+D~H2xL6y<1}Mr^&gazYpIU#J%{hb>)-MQ-2c`$ zVQ}amwuQUV##+!CYC&758Lgofw1%3oG`CnztXT(jyeY{wjDVf+q`h*@U%7_D;)?Y9 z^!F+WWXcA-ViVP5%WC?5386MA)oT>a19+$^3I%yg){807>?0~u-O2y^R=AC|L_hVf z$tU+8yc?~dX0);!L|P4B9RI at FvF+7-FBv0&8iyP1xr)LOo*ag*idaKUA-v|cT`FG5 z4*0?pWF=Kn)6|{^M_wVqV5l5|k9y`EnR`-pP}66B at s-%${_-0s6zd|Niwxeezn<@Z zVSK!N3?w}!*T7YW)a=-U@{=F`1k>s3F=HtWwqc?!w at 7?RuF5S66??2@ z)+O%RxmQOE+K(6tdOL}Ixhx31Ii>R-VIWHtr6v8YG6Ug{|NC>pt)Z5&)=&$HVRz>A zXK&(c4f?xFsAnrE19)Axut>pCT1%L(7K%~9iqPHNr7DnV>ghd?1!}{-fkEwoaI&BT zUAa;jYPot;nNUttu5#CX^!^t=6ZzmzpGg6D0Yn~?nP1G{AI86UeO=N>Esik8l8vHV z)mjmvK!nV6o3*NSaQE$gU68c`VG((q7yRv4=pE*<-zp{7(f at cd)*5O_$Rbq$ zc=;E<#NU19nerdGJs`mbZBdm<7yxh%K!P!rLUBvR_QPCh)lCFd zT&R?)b;4nr%o0X~uS>4?eeXoLHPn)5ld!kC79ai4pO*iV;uIQ{MsSxH8;^*wGF4hD zb&a%Nk6e}PxAK)d`LS^uOkmu9=W87i>gDAHEUnfb$vm*Bx7J at B5}y--Y$wD3N*(PS z%|LHZ8DmrM2ZHYAS52&8&@kv7(xf`V#JKm6|Z at y)M%ol>=y zjF4$~bHv_=_?#3aE43rrX4#hUhN|_-iqaR}w|jTZK}?IQ%a~hUL~i+t>?Px~DKR-X2IzK--27M4Ax{mG&y=1l99=2a#(r|>K zAY*~1*iWRw at S62CCc&7fiZdTi;N|QLm7=Hg4#+0klK>_eW1KN&Gsfa7&)Kb}T$Mb4 zO4Zub(u~*NeqcjVy>xXBiz{@&ReLt|$aUtPJ3e4#*o- at dl3vR}>i>0-YgOrVf^l#{9L zb$L5sd|BcXmAt-W2?>Pi!1f{4#0mgU{=o+^pPO6z<0SQcIOj>mSR5Xmo<@M{k;r94 zn{caWo4ru2;9Ob3h}}DPU{B9&71io1S1x1W+Er=yUXy}D4inhau&_4x{{gXBSSVJy zsYDvG)oY~eqjJ%uESr}GL2A(EL;X-qtWSUBlX(8SKV19cafyaj48UXn=2kh;P79KC zWRNsFn7Hm$>vCR6UTgo3+i-V(z-nd`ZQ>3ZhMU(6sttV0mSPi z*-FvEM`S-Sza~Ggb at P@E4DPzMDF58 at B4*})EuC2VH*Is1f}>>O6CzAFNgH*~wH`$g zF?Pc(mMUT%5Ldn*xTrJs8 zSGXpZ*mm#Sfj8bUc+1Z(U7f=#SAMIk7w+1;L+0hPnpJF~BG(KIHX`+~X$57(3OL-R z=zH&d=os!-)(F`be}xXBzqvZ6tmPZbCETcp5MQrWau_yEe+#k7+^4Vm+M5scqwl@XK~lo9MifXChu0QPzWd!1ZWrQpcOZDow%o;&wfB-Xj*MWw_F0C#onlzj`` zqJ*geWc*|_kdmuUP6BE)Vy$~jHf?D`|3^lZHNx~azlW#Z^#m5 at 7S{VU<%MQA=d+yi zD1e9IqwStLF|^)V98#)UR}18ap*OWO<1GgdRm@{8?XjvvM{^tYZ;|c}GRiera3s^0#s3eIMP3SSP&9bLO0^EOUwBcyn0oA;OT+RU9xX6b+mI-n}}M%BJzO0(r_Xky?3MU zxsF5b9;@U2*?g!U+m0So@<0^avTOOJ?I#XPe~{(*MSSi(r|@r||7tD2p4IKFQ_gvkb8Z3H2jFyo)NG<6 zxvEORp-`^j?k*f29IjY(sf1UqT$Y~4S_%6*`(+0*)jZJ+x%x(}8*;5ptwt#8zEUgK z at I(92en*eghxngwJ&(l53HE83B@>3O9JO_p at k z>M{kVrL6 at ABX^=_%lh?t7gnxHEor!(YP~mnyX at O!k9Lmg<~kiFoN#_|3saM;4TDOU zLa{QA*X^_JxNO?eh8=$>Pqki~zl!gj`5JyS{;hhIzAwt7ig}*~kXTcP+JgS4?W{Fs zthMB-Z3<4Pr3rWK8dz7UUMFx~z^|@c_M}xCRJArLsEyHjjEa#4Xy0)FNnKo;obwE0 zEQ>1H6x-f?P+AqH%(s7n??3g=n0xtByp)B>STsYk6rA==?TBpeuSuzvV{vtv{5;lL at rG@8sJfL=t{y{7?g20QRKi}b*JPT8 zCdcB{NUpa8eRe&xpIWtM0mQ#F^x+hoS1gYEfZ;%aC zYp5xNp6+f$`gS7RvBl9nE-5Y)Q9}QwZ7T9w0nJiy$`B#Cj$al7>iJTS!9*22mWAS~ zJ!S7Y>(hc6Hh^0y;`h9pEcGS}ApVs at CyS(kkHlOMMIcmbjbwX$zgCcKInjEtg)+n# z3vDQ<$kr~OQ;e~wn6puZ zs&*KF-F)%zSvGj#SUKAdQ$IvuIgjSH7Id_?qkGF%?CsfJvG9Xac%@no_a0CY#N=cV zRs!N8^4jk^iua{7MyKlBZ>4ezn^KGQFWR%>@a*f+tKo|y+S3FUz1DpF)xq|^cQ*bC3d%rCBu?F!*7*rplLjcgSvlE?f zjnq!43)e2^=a;|Uva|CqfBN>%r6rBC9K3P&`-Nze0Fr`a6B3nd1h|oka}zEeK3gJ3 z*J|nb%o(Yc)a9iG<(<^k+5xNgwJL9Eo2j7%#yloh%Zw+_$@LMS=n`HJ`T6AxIDXW$ zwe70_?4LgP_n8{KBazZQoQx+Ed0rdIGR9J39>`F!)yb6@(xQMCI(s1cn3CszQ)I>L)T{?%%zqh*$_VT_G0_~J{v$rcmkaw z=Hk0?(?vBC?5vp6vItf#xgMW66M at 7W+J$RN%JW*^cH2ShXjfi4U00Q^r_xM6hE3 zCS_bdjS;}5$WhtJq9K;O~IjD?6of5Ei7Ehu>M??g>@s47^-Fwc7s~MVU+18gMp07K zs+zX0QeDCe*OrvD`kkFS at s91D zRh`q>B at 9B+v2}bop%$s5-N#Ktry*A{zO1r;#uXcD1_EL}W~s-BOyz3HY!DU7^?}~~ zcw67=yzF;lk$Q_HXmjCmE*4Q!Kthj&n6mwb%ZxauVnj=0jWIUtv#pGbZ4y z>8FV=n{(Nx5ks!pzy{5hNQr!$dNZa}AA%tEhKI$+!usWME%>Kk31wQLEsb0uIR!^n z;fU_GE%?11_o^-sQEeek8glhak;`cNF_-Q;DsnY$VSUQ|qr2YZMb#z0t5!)Ww+{QOH+9a@&QYxgqXf))II+Tvu_Wk&mr9u6oF at pLlgb63g#i`3+{zf2 zX|NGrdw?;f^O{C!q}=4O8*@Opo4C7t9-iY4TtvYt}82p0>(RDmgbs~@? zO=z`NBC;6KwZeXGYolEKqgu-iL&9sFBu?Fm=-lOX z-s*;fS?9dgN*1Xf7kuFcic2I_ptv6wB at E;+Ij%;zmN2bo-#i7{*cqEKW@!|>I0oQ^ zOm6~pw6InwIQ^Tp;b7NZ-S$+gEygkU1VoirvcmdLDSGCJ at C=+#aJ!g{Ndt1+JhF}YprCj_C|sw`L$1ss*ERLk)w=iD5&&^YQiTGZvgz^r(tg7iV#KX#qfS54E?o6Fb_&xV_^x-6DSLB_GRYsvF-5;6`9o1nOOMHyKHs^O&Uewm}nkF>3N$N&CeDFsbmC`&6fONphjCT^mvWQj`XG z*IYmyc709-<09xWlR at r}#tYZz722ln;W^ZfH2RcHnJw8;X>kTUFXy<6! zhl@%az)7>b$|qLQ-WejpVV}vlCGQ)q=vEV)^QZ^!7ZC=qDi6?Ulc-_GF^Qg z)2N{)fnUhg3Q)&9ezbGcEXe*w7J#LKSjD~`1{kNz_2dK at CJcbuBCtQouQPBg&$A9iX~YfY{q1!usg9g_oaD1gCBjX57aIx1B<6xv6f&c&k z)k#D_R2q at 0fqx)ltYrOAqgtftM8w<)0;!%taSO<`C~DUHWi20e(5VJI at Z8UsMzLnA zHi08+KoXg4j0LF#lVObIKwHHq=A-wY#f at 6Qarm#mOip+S5|nFz))ku0&rfn6bx;>!rX6z`N2r_ at +w zpCLt$P&$z-1%>BG0~))9&(BY0pl_sbL%4tq3=9mU5Kob8ODEVwaN|T9H*VyqGUGaf zqNmC;!%|Cf)%X;gX#fdR8`!|Wz(6|j)};D%jhoQbEv(yq>x3Xxqf`wH3=AYf1Q+>! zt<{xWEe)O_3z4F6v~x6LhP;7+fq{YF$}s2Q*o at 5n1MT zqkAJVO#?`oR2l;V0|SFVlWPUCji4A&W{DqJW&d3*zbuOzsUsQjNdw3jWolqxU|=8% Z{}1Y at 9!8I54Uhl;002ovPDHLkV1hrg^929^ literal 0 HcmV?d00001 -- 2.7.4 From helin.zhang at intel.com Fri Mar 30 05:40:07 2018 From: helin.zhang at intel.com (Zhang, Helin) Date: Fri, 30 Mar 2018 03:40:07 +0000 Subject: [dpdk-web] [PATCH] add DPVS logo in the ecosystem In-Reply-To: <1522380839-10202-1-git-send-email-raychen@qiyi.com> References: <1522380839-10202-1-git-send-email-raychen@qiyi.com> Message-ID: > -----Original Message----- > From: Lei Chen [mailto:raychen at qiyi.com] > Sent: Friday, March 30, 2018 11:34 AM > To: thomas at monjalon.net; Zhang, Helin > Cc: web at dpdk.org; raychen at qiyi.com; jiangwenjie at qiyi.com > Subject: [PATCH] add DPVS logo in the ecosystem > > Replace text link to PNG logo link for DPVS, a high performance Layer-4 load > balancer based on DPDK. > > Signed-off-by: Lei Chen Acked-by: Helin Zhang BTW, I don't know how to check the patch integrated. I'd reply on Thomas to double check. From raychen at qiyi.com Fri Mar 30 06:34:11 2018 From: raychen at qiyi.com (=?gb2312?B?s8LA16OocmF5Y2hlbqOpLby8yvWy+sa31tDQxA==?=) Date: Fri, 30 Mar 2018 04:34:11 +0000 Subject: [dpdk-web] =?gb2312?b?tPC4tDogW1BBVENIXSBhZGQgRFBWUyBsb2dvIGlu?= =?gb2312?b?IHRoZSBlY29zeXN0ZW0=?= In-Reply-To: References: <1522380839-10202-1-git-send-email-raychen@qiyi.com>, Message-ID: <1522384451142.85349@qiyi.com> Ok, if needed, we can send you the PNG file as attachment. ________________________________________ ???: Zhang, Helin ????: 2018?3?30? 11:40 ???: ???raychen?-??????; thomas at monjalon.net ??: web at dpdk.org; ??? ??: RE: [PATCH] add DPVS logo in the ecosystem > -----Original Message----- > From: Lei Chen [mailto:raychen at qiyi.com] > Sent: Friday, March 30, 2018 11:34 AM > To: thomas at monjalon.net; Zhang, Helin > Cc: web at dpdk.org; raychen at qiyi.com; jiangwenjie at qiyi.com > Subject: [PATCH] add DPVS logo in the ecosystem > > Replace text link to PNG logo link for DPVS, a high performance Layer-4 load > balancer based on DPDK. > > Signed-off-by: Lei Chen Acked-by: Helin Zhang BTW, I don't know how to check the patch integrated. I'd reply on Thomas to double check. From thomas at monjalon.net Sat Mar 31 03:07:28 2018 From: thomas at monjalon.net (Thomas Monjalon) Date: Sat, 31 Mar 2018 03:07:28 +0200 Subject: [dpdk-web] [PATCH] add DPVS logo in the ecosystem In-Reply-To: References: <1522380839-10202-1-git-send-email-raychen@qiyi.com> Message-ID: <2046337.RICnAgynS7@xps> 30/03/2018 05:40, Zhang, Helin: > From: Lei Chen [mailto:raychen at qiyi.com] > > > > Replace text link to PNG logo link for DPVS, a high performance Layer-4 load > > balancer based on DPDK. > > > > Signed-off-by: Lei Chen > Acked-by: Helin Zhang > > BTW, I don't know how to check the patch integrated. I'd reply on Thomas to double check. The logo is clean. Applied, thanks