From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Nowak, DamianX" <damianx.nowak@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 1/1] test: new test structure for asymmetric crypto
Date: Wed, 27 Mar 2019 11:26:21 +0000 [thread overview]
Message-ID: <06EE24DD0B19E248B53F6DC8657831551B14E109@hasmsx109.ger.corp.intel.com> (raw)
Message-ID: <20190327112621.ovk6V-gNpRr6lKn2Xt8m-xWjSgFVWRavmM9HaTF8PaA@z> (raw)
In-Reply-To: <20190327094521.16414-2-damianx.nowak@intel.com>
> -----Original Message-----
> From: Nowak, DamianX
> Sent: Wednesday, March 27, 2019 10:45 AM
> To: dev@dpdk.org
> Cc: Trahe, Fiona <fiona.trahe@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>; Nowak, DamianX
> <damianx.nowak@intel.com>
> Subject: [PATCH v5 1/1] test: new test structure for asymmetric crypto
>
> This patch adds new test structure for modexp
> and modinv for asymmetric cryptography
>
> Signed-off-by: Damian Nowak <damianx.nowak@intel.com>
> ---
> app/test/test_cryptodev.h | 1 +
> app/test/test_cryptodev_asym.c | 318 ++++++++++
> app/test/test_cryptodev_mod_test_vectors.h | 967
> +++++++++++++++++++++++++++++
> 3 files changed, 1286 insertions(+)
>
> diff --git a/app/test/test_cryptodev.h b/app/test/test_cryptodev.h
> index a73a49e..14b54dc 100644
> --- a/app/test/test_cryptodev.h
> +++ b/app/test/test_cryptodev.h
> @@ -54,6 +54,7 @@
> #define CRYPTODEV_NAME_AESNI_GCM_PMD crypto_aesni_gcm
> #define CRYPTODEV_NAME_OPENSSL_PMD crypto_openssl
> #define CRYPTODEV_NAME_QAT_SYM_PMD crypto_qat
> +#define CRYPTODEV_NAME_QAT_ASYM_PMD crypto_qat_asym
> #define CRYPTODEV_NAME_SNOW3G_PMD crypto_snow3g
> #define CRYPTODEV_NAME_KASUMI_PMD crypto_kasumi
> #define CRYPTODEV_NAME_ZUC_PMD crypto_zuc
> diff --git a/app/test/test_cryptodev_asym.c
> b/app/test/test_cryptodev_asym.c
> index a779e8f..2fe5b8f 100644
> --- a/app/test/test_cryptodev_asym.c
> +++ b/app/test/test_cryptodev_asym.c
> @@ -1,5 +1,6 @@
> 2.7.4
Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
next prev parent reply other threads:[~2019-03-27 11:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 16:38 [dpdk-dev] [PATCH] test: add new test structure for asymmetric cryptography Damian Nowak
2019-03-04 16:09 ` [dpdk-dev] [PATCH v2] " Damian Nowak
2019-03-12 9:36 ` [dpdk-dev] [PATCH v3 0/1] test: new test structure for asymmetric crypto Damian Nowak
2019-03-12 9:36 ` [dpdk-dev] [PATCH v3 1/1] " Damian Nowak
2019-03-26 14:15 ` [dpdk-dev] [PATCH v4 0/1] " Damian Nowak
2019-03-26 14:15 ` Damian Nowak
2019-03-26 14:15 ` [dpdk-dev] [PATCH v4 1/1] " Damian Nowak
2019-03-26 14:15 ` Damian Nowak
2019-03-27 9:45 ` [dpdk-dev] [PATCH v5 0/1] " Damian Nowak
2019-03-27 9:45 ` Damian Nowak
2019-03-27 9:45 ` [dpdk-dev] [PATCH v5 1/1] " Damian Nowak
2019-03-27 9:45 ` Damian Nowak
2019-03-27 11:26 ` Kusztal, ArkadiuszX [this message]
2019-03-27 11:26 ` Kusztal, ArkadiuszX
2019-03-28 12:16 ` Trahe, Fiona
2019-03-28 12:16 ` Trahe, Fiona
2019-03-29 14:29 ` Akhil Goyal
2019-03-29 14:29 ` Akhil Goyal
2019-07-25 7:18 ` Shally Verma
2019-07-25 8:35 ` Kusztal, ArkadiuszX
2019-07-25 9:17 ` Shally Verma
2019-07-25 9:38 ` Kusztal, ArkadiuszX
2019-07-25 16:51 ` Shally Verma
2019-07-25 17:51 ` Kusztal, ArkadiuszX
2019-07-26 5:29 ` Shally Verma
2019-07-26 7:57 ` Kusztal, ArkadiuszX
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=06EE24DD0B19E248B53F6DC8657831551B14E109@hasmsx109.ger.corp.intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=damianx.nowak@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).