From mboxrd@z Thu Jan  1 00:00:00 1970
From: "O'Driscoll, Tim" <tim.o'driscoll@intel.com>
Subject: Re: DPDK 2.2 roadmap
Date: Fri, 11 Sep 2015 08:08:34 +0000
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA6740480C@IRSMSX108.ger.corp.intel.com>
References: <1882381.9qlZTmz9zB@xps13>
 <26FA93C7ED1EAA44AB77D62FBE1D27BA67401646@IRSMSX108.ger.corp.intel.com>
 <2207263.dDyMmkz5Pr@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "dev@dpdk.org" <dev@dpdk.org>
To: 'Thomas Monjalon' <thomas.monjalon@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id 04DF29E5
 for <dev@dpdk.org>; Fri, 11 Sep 2015 10:08:37 +0200 (CEST)
In-Reply-To: <2207263.dDyMmkz5Pr@xps13>
Content-Language: en-US
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, September 10, 2015 1:44 PM
> To: O'Driscoll, Tim
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] DPDK 2.2 roadmap
>
> 2015-09-09 12:56, O'Driscoll, Tim:
> > DCB for i40e &X550:  DCB support will be extended to the i40e and X550
> NICs.
>
> A patch for DCB on X550 is already applied but the release notes part
> was forgotten.
>
> > IPsec Sample App:  A sample application will be provided to show how
> the
> > cryptodev library can be used to implement IPsec. This will be based
> on
> > the NetBSD IPsec implementation.
>
> For each API, it is really interesting to have some unit tests and some
> examples to show how it should be used. However adding an IPsec stack
> looks
> to be beyond the need of an API example. It may be big and difficult to
> maintain when updating DPDK.
> Why not spawn a new project here: http://dpdk.org/browse/ ?

What we're planning is a sample application that shows how hardware and sof=
tware crypto accelerators can be used to accelerate a typical workload, whi=
ch happens to be IPsec. We plan to provide an RFC next week which will give=
 further details on what's being proposed. We don't expect maintenance to b=
e a problem, but we can discuss that further when the scope has been clarif=
ied.