From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"Griffin, John" <john.griffin@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] app/test: add AES GCM performance test to cryptodev
Date: Wed, 28 Sep 2016 00:45:21 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973CA003F8@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1474984172-11838-1-git-send-email-arkadiuszx.kusztal@intel.com>
Hi Arek,
> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Tuesday, September 27, 2016 6:50 AM
> To: dev@dpdk.org
> Cc: Trahe, Fiona; Jain, Deepak K; De Lara Guarch, Pablo; Griffin, John; Kusztal,
> ArkadiuszX
> Subject: [PATCH v3] app/test: add AES GCM performance test to cryptodev
>
> This patch adds AES Galois Counter Mode performance test case
> for cryptodev QAT and AESNI GCM. 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.
>
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> This patch depends on the following patches/patchsets:
>
> "app/test: fix linkage scope of gmac plaintext array"
> (http://dpdk.org/dev/patchwork/patch/16023/)
>
> v2:
> * Fixed 32b build problem in test_cryptodev_perf.c
> v3:
> * Added multiple test cases possibility
> * Added AESNI GCM test suite
> ---
> app/test/test_cryptodev_gcm_test_vectors.h | 632
> +++++++++++++++++++++++++++++
> app/test/test_cryptodev_perf.c | 482 +++++++++++++++++++++-
> 2 files changed, 1111 insertions(+), 3 deletions(-)
>
> diff --git a/app/test/test_cryptodev_perf.c b/app/test/test_cryptodev_perf.c
> index 20713d4..3bb6f34 100644
> --- a/app/test/test_cryptodev_perf.c
> +++ b/app/test/test_cryptodev_perf.c
> @@ -41,6 +41,7 @@
[...]
> +static int
> +perf_AES_GCM(uint8_t dev_id, uint16_t queue_id,
> + struct perf_test_params *pparams, uint32_t test_ops)
> +{
[...]
> + if (burst_dequeued == 0)
> + failed_polls++;
> + else {
> + processed += burst_dequeued;
> +
> + for (m = 0; m < burst_dequeued; m++) {
> + if (test_ops) {
> + uint16_t iv_pad_len =
> ALIGN_POW2_ROUNDUP
> + (pparams->symmetric_op->iv_len,
> 16);
> + uint8_t *pkt = rte_pktmbuf_mtod(
> + proc_ops[m]->sym->m_src,
> + uint8_t *);
> +
> + TEST_ASSERT_BUFFERS_ARE_EQUAL(
> + pparams->symmetric_op->c_data,
> + pkt + iv_pad_len +
> + pparams->symmetric_op->aad_len,
> + pparams->symmetric_op->c_len,
> + "GCM Ciphertext data not as
> expected");
> +
> + TEST_ASSERT_BUFFERS_ARE_EQUAL(
> + pparams->symmetric_op->t_data,
> + pkt + iv_pad_len +
> + pparams->symmetric_op->aad_len +
> + pparams->symmetric_op->c_len,
> + pparams->symmetric_op->t_len,
> + "GCM MAC data not as expected");
> +
> + }
> + rte_crypto_op_free(proc_ops[m]);
> + }
Please, check the indentation here. Checkpatch complained here.
Thanks,
Pablo
> + }
> + }
> +
> + tsc_end = rte_rdtsc_precise();
> +
> + double ops_s = ((double)processed / (tsc_end - tsc_start))
> + * rte_get_tsc_hz();
> + double throughput = (ops_s * pparams->symmetric_op->p_len * 8)
> + / 1000000000;
prev parent reply other threads:[~2016-09-28 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 13:49 Arek Kusztal
2016-09-28 0:45 ` 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=E115CCD9D858EF4F90C690B0DCB4D8973CA003F8@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=arkadiuszx.kusztal@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).