DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>,
	Declan Doherty <declan.doherty@intel.com>,
	Fan Zhang <royzhang1980@gmail.com>,
	Ashish Gupta <ashishg@marvell.com>, Ray Kinsella <mdr@ashroe.eu>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "acc@openeuler.org" <acc@openeuler.org>
Subject: RE: [EXT] [PATCH resend v5 6/6] test/crypto: add cryptodev_uadk_autotest
Date: Tue, 25 Oct 2022 14:54:36 +0000	[thread overview]
Message-ID: <CO6PR18MB4484736EB9CDB861ED657A48D8319@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20221024134409.1896776-7-zhangfei.gao@linaro.org>

> Subject: [EXT] [PATCH resend v5 6/6] test/crypto: add cryptodev_uadk_autotest
Rewrite patch title as
test/crypto: support uadk PMD

> 
Add a line
Updated test application to run autotest for uadk crypto PMD.
> Example:
> sudo dpdk-test --vdev=crypto_uadk --log-level=6
> RTE>>cryptodev_uadk_autotest
> RTE>>quit

Add this information in uadk.rst as well.

> 
> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
> ---
>  app/test/test_cryptodev.c | 7 +++++++
>  app/test/test_cryptodev.h | 1 +
>  2 files changed, 8 insertions(+)
> 
> diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
> index c2b33686ed..183e24f150 100644
> --- a/app/test/test_cryptodev.c
> +++ b/app/test/test_cryptodev.c
> @@ -16467,6 +16467,12 @@ test_cryptodev_qat(void)
>  	return
> run_cryptodev_testsuite(RTE_STR(CRYPTODEV_NAME_QAT_SYM_PMD));
>  }
> 
> +static int
> +test_cryptodev_uadk(void)
> +{
> +	return
> run_cryptodev_testsuite(RTE_STR(CRYPTODEV_NAME_UADK_PMD));
> +}
> +
>  static int
>  test_cryptodev_virtio(void)
>  {
> @@ -16810,6 +16816,7 @@
> REGISTER_TEST_COMMAND(cryptodev_sw_mvsam_autotest,
> test_cryptodev_mrvl);
>  REGISTER_TEST_COMMAND(cryptodev_dpaa2_sec_autotest,
> test_cryptodev_dpaa2_sec);
>  REGISTER_TEST_COMMAND(cryptodev_dpaa_sec_autotest,
> test_cryptodev_dpaa_sec);
>  REGISTER_TEST_COMMAND(cryptodev_ccp_autotest, test_cryptodev_ccp);
> +REGISTER_TEST_COMMAND(cryptodev_uadk_autotest, test_cryptodev_uadk);
>  REGISTER_TEST_COMMAND(cryptodev_virtio_autotest, test_cryptodev_virtio);
>  REGISTER_TEST_COMMAND(cryptodev_octeontx_autotest,
> test_cryptodev_octeontx);
>  REGISTER_TEST_COMMAND(cryptodev_caam_jr_autotest,
> test_cryptodev_caam_jr);
> diff --git a/app/test/test_cryptodev.h b/app/test/test_cryptodev.h
> index 29a7d4db2b..abd795f54a 100644
> --- a/app/test/test_cryptodev.h
> +++ b/app/test/test_cryptodev.h
> @@ -74,6 +74,7 @@
>  #define CRYPTODEV_NAME_CN9K_PMD		crypto_cn9k
>  #define CRYPTODEV_NAME_CN10K_PMD	crypto_cn10k
>  #define CRYPTODEV_NAME_MLX5_PMD		crypto_mlx5
> +#define CRYPTODEV_NAME_UADK_PMD		crypto_uadk
> 
> 
Add the newly added autotest in "app/test/meson.build" in driver_test_names[]

  reply	other threads:[~2022-10-25 14:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 13:44 [PATCH resend v5 0/6] crypto/uadk: introduce uadk crypto driver Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 1/6] " Zhangfei Gao
2022-10-25 14:08   ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 2/6] crypto/uadk: support basic operations Zhangfei Gao
2022-10-25 14:18   ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 3/6] crypto/uadk: support enqueue/dequeue operations Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 4/6] crypto/uadk: support cipher algorithms Zhangfei Gao
2022-10-25 14:28   ` [EXT] " Akhil Goyal
2022-10-24 13:44 ` [PATCH resend v5 5/6] crypto/uadk: support auth algorithms Zhangfei Gao
2022-10-25 14:38   ` [EXT] " Akhil Goyal
2022-10-26 10:02     ` Zhangfei Gao
2022-10-24 13:44 ` [PATCH resend v5 6/6] test/crypto: add cryptodev_uadk_autotest Zhangfei Gao
2022-10-25 14:54   ` Akhil Goyal [this message]
2022-10-26  9:57     ` [EXT] " Zhangfei Gao
2022-10-25 14:59 ` [EXT] [PATCH resend v5 0/6] crypto/uadk: introduce uadk crypto driver Akhil Goyal
2022-10-26  9:53   ` Zhangfei Gao
2022-10-26 10:16     ` Akhil Goyal

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=CO6PR18MB4484736EB9CDB861ED657A48D8319@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=acc@openeuler.org \
    --cc=ashishg@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    --cc=royzhang1980@gmail.com \
    --cc=thomas@monjalon.net \
    --cc=zhangfei.gao@linaro.org \
    /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).