DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/4] New crypto algorithm string parser API
Date: Tue, 28 Feb 2017 14:18:40 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D897476E3FEF@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1488206326-70385-1-git-send-email-pablo.de.lara.guarch@intel.com>



> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Monday, February 27, 2017 2:39 PM
> To: Doherty, Declan
> Cc: dev@dpdk.org; De Lara Guarch, Pablo
> Subject: [PATCH v2 0/4] New crypto algorithm string parser API
> 
> Last release, an array with strings for the supported algorithms
> by the cryptodev library was added and used in the crypto-perf app.
> 
> This patchset creates a new API to parse strings from the user,
> to select the desired algorithm (using the array above),
> which can be used by any application, making it consistent across
> all the applications (now, L2fwd-crypto and crypto-perf apps are
> using different strings).
> 
> Changes in v2:
> 
> - Modified L2fwd-crypto document to reflect the changes
> 
> Pablo de Lara (4):
>   cryptodev: add missing algorithm strings
>   cryptodev: add algorithm string parsers
>   app/crypto-perf: use cryptodev algorithm parser
>   examples/l2fwd-crypto: use cryptodev algorithm parser
> 
>  app/test-crypto-perf/cperf_options_parsing.c   | 206 ++-----------------------
>  doc/guides/sample_app_ug/l2_forward_crypto.rst |  10 +-
>  examples/l2fwd-crypto/main.c                   |  85 ++--------
>  lib/librte_cryptodev/rte_cryptodev.c           |  38 +++++
>  lib/librte_cryptodev/rte_cryptodev.h           |  30 ++++
>  lib/librte_cryptodev/rte_cryptodev_version.map |   8 +
>  6 files changed, 105 insertions(+), 272 deletions(-)
> 
> --
> 2.7.4

Applied to dpdk-next-crypto.

Pablo

      parent reply	other threads:[~2017-02-28 14:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 12:33 [dpdk-dev] [PATCH " Pablo de Lara
2017-02-23 12:33 ` [dpdk-dev] [PATCH 1/4] cryptodev: add missing algorithm strings Pablo de Lara
2017-02-23 12:33 ` [dpdk-dev] [PATCH 2/4] cryptodev: add algorithm string parsers Pablo de Lara
2017-02-23 12:33 ` [dpdk-dev] [PATCH 3/4] app/crypto-perf: use cryptodev algorithm parser Pablo de Lara
2017-02-23 12:33 ` [dpdk-dev] [PATCH 4/4] examples/l2fwd-crypto: " Pablo de Lara
2017-02-24 15:41 ` [dpdk-dev] [PATCH 0/4] New crypto algorithm string parser API Trahe, Fiona
2017-02-25 11:18   ` Hemant Agrawal
2017-02-27 14:38 ` [dpdk-dev] [PATCH v2 " Pablo de Lara
2017-02-27 14:38   ` [dpdk-dev] [PATCH v2 1/4] cryptodev: add missing algorithm strings Pablo de Lara
2017-02-27 14:38   ` [dpdk-dev] [PATCH v2 2/4] cryptodev: add algorithm string parsers Pablo de Lara
2017-02-27 14:38   ` [dpdk-dev] [PATCH v2 3/4] app/crypto-perf: use cryptodev algorithm parser Pablo de Lara
2017-02-27 14:38   ` [dpdk-dev] [PATCH v2 4/4] examples/l2fwd-crypto: " Pablo de Lara
2017-02-28 14:18   ` De Lara Guarch, Pablo [this message]

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=E115CCD9D858EF4F90C690B0DCB4D897476E3FEF@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).