From: "O'Driscoll, Tim" <tim.o'driscoll@intel.com>
To: 'Thomas Monjalon' <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: DPDK 2.2 roadmap
Date: Fri, 11 Sep 2015 08:08:34 +0000 [thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA6740480C@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <2207263.dDyMmkz5Pr@xps13>
> -----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 software crypto accelerators can be used to accelerate a typical workload, which 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 be a problem, but we can discuss that further when the scope has been clarified.
next prev parent reply other threads:[~2015-09-11 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 8:44 DPDK 2.2 roadmap Thomas Monjalon
2015-09-09 12:56 ` O'Driscoll, Tim
2015-09-10 12:43 ` Thomas Monjalon
2015-09-10 13:26 ` Thomas F Herbert
2015-09-10 19:27 ` Flavio Leitner
2015-09-10 19:55 ` Thomas Monjalon
2015-09-11 1:23 ` Yuanhan Liu
2015-09-11 8:08 ` O'Driscoll, Tim [this message]
2015-09-14 8:40 ` Zhang, Helin
2015-09-14 8:57 ` Thomas Monjalon
2015-09-15 20:11 ` Olga Shern
2015-09-09 17:48 ` Patel, Rashmin N
2015-09-09 18:00 ` Stephen Hemminger
2015-09-15 9:16 ` David Marchand
-- strict thread matches above, loose matches on Subject: below --
2015-09-14 13:44 Matej Vido
2015-09-14 14:02 ` Thomas Monjalon
2015-09-14 15:37 ` Matej Vido
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26FA93C7ED1EAA44AB77D62FBE1D27BA6740480C@IRSMSX108.ger.corp.intel.com \
--to=tim.o'driscoll@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.