From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] New crypto algorithm string parser API
Date: Fri, 24 Feb 2017 15:41:18 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589197B38@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1487853218-113232-1-git-send-email-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Thursday, February 23, 2017 12:34 PM
> To: Doherty, Declan <declan.doherty@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH 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).
>
> 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 ++-----------------------
> 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 +
> 5 files changed, 100 insertions(+), 267 deletions(-)
>
> --
> 2.7.4
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2017-02-24 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 12:33 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 ` Trahe, Fiona [this message]
2017-02-25 11:18 ` [dpdk-dev] [PATCH 0/4] New crypto algorithm string parser API 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 ` [dpdk-dev] [PATCH v2 0/4] New crypto algorithm string parser API De Lara Guarch, Pablo
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=348A99DA5F5B7549AA880327E580B43589197B38@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).