From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Jain, Deepak K" <deepak.k.jain@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>,
"Griffin, John" <john.griffin@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] Extending cryptodev Performance tests
Date: Thu, 16 Jun 2016 22:13:55 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C9637A0@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1466106543-209204-1-git-send-email-deepak.k.jain@intel.com>
> -----Original Message-----
> From: Jain, Deepak K
> Sent: Thursday, June 16, 2016 8:49 PM
> To: dev@dpdk.org
> Cc: Doherty, Declan; Griffin, John; Trahe, Fiona; De Lara Guarch, Pablo; Jain,
> Deepak K
> Subject: [PATCH 0/4] Extending cryptodev Performance tests
>
> Performance tests haven been extended in this patchset.
>
> Patchset consists of 4 patches:
> Patch 1 adds new function rte_crypto_op_bulk_free to be used in patch 2
> and patch 3.
> Patch 2 add snow3g performance tests.
> Patch 3 updates the existing aes performanc test
> Patch 4 fixes the typo in names of perftest
>
>
> Declan Doherty (1):
> cryptodev: add rte_crypto_op_bulk_free function
>
> Fiona Trahe (2):
> app/test: adding Snow3g performance test
> app/test: updating AES SHA performance test
>
> Jain, Deepak K (1):
> app/test: typo fixing
>
> app/test/test_cryptodev.h | 4 +-
> app/test/test_cryptodev_perf.c | 1153
> ++++++++++++++++++++++++++++++++-----
> lib/librte_cryptodev/rte_crypto.h | 15 +
> 3 files changed, 1030 insertions(+), 142 deletions(-)
>
> --
> 2.5.5
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2016-06-16 22:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 19:48 Jain, Deepak K
2016-06-16 19:49 ` [dpdk-dev] [PATCH 1/4] cryptodev: add rte_crypto_op_bulk_free function Jain, Deepak K
2016-06-20 9:45 ` Thomas Monjalon
2016-06-20 14:30 ` Jain, Deepak K
2016-06-16 19:49 ` [dpdk-dev] [PATCH 2/4] app/test: adding Snow3g performance test Jain, Deepak K
2016-06-16 19:49 ` [dpdk-dev] [PATCH 3/4] app/test: updating AES SHA " Jain, Deepak K
2016-06-16 19:49 ` [dpdk-dev] [PATCH 4/4] app/test: typo fixing Jain, Deepak K
2016-06-16 22:13 ` De Lara Guarch, Pablo [this message]
2016-06-20 14:32 ` [dpdk-dev] [PATCH v2 0/3] Extending cryptodev Performance tests Jain, Deepak K
2016-06-20 14:32 ` [dpdk-dev] [PATCH v2 1/3] app/test: adding Snow3g performance test Jain, Deepak K
2016-06-20 14:32 ` [dpdk-dev] [PATCH v2 2/3] app/test: updating AES SHA " Jain, Deepak K
2016-06-20 14:32 ` [dpdk-dev] [PATCH v2 3/3] app/test: typo fixing Jain, Deepak K
2016-06-20 15:08 ` [dpdk-dev] [PATCH v3 0/3] Extending cryptodev Performance tests Jain, Deepak K
2016-06-20 15:08 ` [dpdk-dev] [PATCH v3 1/3] app/test: adding Snow3g performance test Jain, Deepak K
2016-06-20 15:08 ` [dpdk-dev] [PATCH v3 2/3] app/test: updating AES SHA " Jain, Deepak K
2016-06-20 15:08 ` [dpdk-dev] [PATCH v3 3/3] app/test: typo fixing Jain, Deepak K
2016-06-20 15:24 ` [dpdk-dev] [PATCH v3 0/3] Extending cryptodev Performance tests Thomas Monjalon
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=E115CCD9D858EF4F90C690B0DCB4D8973C9637A0@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@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).