From: "O'Donovan, Saoirse" <saoirse.odonovan@intel.com>
To: Aakash Sasidharan <asasidharan@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] test/crypto: add cryptodev reconfig test
Date: Wed, 19 Apr 2023 13:37:45 +0000 [thread overview]
Message-ID: <PH7PR11MB7147507D19B53EC0DE0753698D629@PH7PR11MB7147.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230405074117.2212923-1-asasidharan@marvell.com>
Hi Aakash,
> -----Original Message-----
> From: Aakash Sasidharan <asasidharan@marvell.com>
> Sent: Wednesday 5 April 2023 08:41
> To: Akhil Goyal <gakhil@marvell.com>; Fan Zhang
> <fanzhang.oss@gmail.com>
> Cc: jerinj@marvell.com; anoobj@marvell.com; dev@dpdk.org;
> asasidharan@marvell.com
> Subject: [PATCH] test/crypto: add cryptodev reconfig test
>
> Add cryptodev tests to verify that the device supports reconfiguration any
> number of times via rte_cryptodev_configure API.
>
> Signed-off-by: Aakash Sasidharan <asasidharan@marvell.com>
> ---
> app/test/test_cryptodev.c | 81
> +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 81 insertions(+)
Tested on the following PMDs: QAT + SW Crypto PMDs
(snow3g, null, chachapoly, kasumi, aesni_mb, aesni_gcm, zuc)
The test results for the testcase were a mix of skipped and passed, based on the capabilities of each PMD, no failures.
Tested-by: Saoirse O'Donovan <saoirse.odonovan@intel.com>
next prev parent reply other threads:[~2023-04-19 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 7:41 Aakash Sasidharan
2023-04-06 14:21 ` Zhang, Fan
2023-04-10 7:19 ` [EXT] " Anoob Joseph
2023-04-18 13:29 ` Zhang, Fan
2023-04-19 13:37 ` O'Donovan, Saoirse [this message]
2023-05-03 7:13 ` 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=PH7PR11MB7147507D19B53EC0DE0753698D629@PH7PR11MB7147.namprd11.prod.outlook.com \
--to=saoirse.odonovan@intel.com \
--cc=anoobj@marvell.com \
--cc=asasidharan@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.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).