From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/test: add AES GCM performance test to cryptodev
Date: Mon, 26 Sep 2016 19:43:30 +0000 [thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C90339463C39@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1474626587-18214-1-git-send-email-arkadiuszx.kusztal@intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Friday, September 23, 2016 11:30 AM
> To: dev@dpdk.org
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; Jain, Deepak K
> <deepak.k.jain@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Griffin, John <john.griffin@intel.com>;
> Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH v2] app/test: add AES GCM performance test to cryptodev
>
> This patch adds AES Galois Counter Mode performance test case for
> cryptodev QAT tests. Test is performed with different buffer sizes, burst size
> of 32 and 128b key. Test vectors are placed in
> app/test/test_cryptodev_perf_vectors.h file.
>
> This patch depends on the following patches/patchsets:
>
> "app/test: fix linkage scope of gmac plaintext array"
> (http://dpdk.org/dev/patchwork/patch/16023/)
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> v2:
> * Fixed 32b build problem in test_cryptodev_perf.c
> ---
> app/test/test_cryptodev_gcm_test_vectors.h | 636
> +++++++++++++++++++++++++++++
> app/test/test_cryptodev_perf.c | 431 ++++++++++++++++++-
> 2 files changed, 1064 insertions(+), 3 deletions(-)
>
> --
> 2.1.0
Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
next prev parent reply other threads:[~2016-09-26 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 10:29 Arek Kusztal
2016-09-26 19:43 ` Jain, Deepak K [this message]
2016-09-26 23:29 ` 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=A09C9DDE180C7E429EC68E2BFB95C90339463C39@IRSMSX107.ger.corp.intel.com \
--to=deepak.k.jain@intel.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=john.griffin@intel.com \
--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).