From: Akhil Goyal <gakhil@marvell.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>,
"ciara.power@intel.com" <ciara.power@intel.com>
Subject: RE: [EXT] [PATCH v2 0/4] Replace obsolote test cases.
Date: Tue, 30 May 2023 10:48:41 +0000 [thread overview]
Message-ID: <CO6PR18MB44848CFA258868AC3AEA140ED84B9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230528173531.263548-1-arkadiuszx.kusztal@intel.com>
> This patchset removes obsolete test cases for RSA, MOD EXP, MOD INV.
> Doing that, new way of handling ut_setup and ut_teardown was proposed.
> Now both behave like constructor/desctuctor to the unit tests.
> It frees particular alghorithm functions from any kind of responsibility to free
> resources.
> The functionality of the tests was extended, but the number of lines of code was
> reduced by ~600 lines.
>
> v2:
> - fixed build problem with non compile-time constant
>
> Arkadiusz Kusztal (4):
> app/test: remove testsuite calls from ut setup
> app/test: refactor mod exp test case
> app/test: refactor mod inv tests
> app/test: add rsa kat and pwct tests
>
> app/test/test_cryptodev_asym.c | 1610 +++++++-------------
> app/test/test_cryptodev_asym_util.h | 28 -
> app/test/test_cryptodev_mod_test_vectors.h | 631 +-------
> app/test/test_cryptodev_rsa_test_vectors.h | 600 ++++----
> 4 files changed, 852 insertions(+), 2017 deletions(-)
>
Fix Doc build.
prev parent reply other threads:[~2023-05-30 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 17:35 Arek Kusztal
2023-05-28 17:35 ` [PATCH v2 1/4] app/test: remove testsuite calls from ut setup Arek Kusztal
2023-05-28 17:35 ` [PATCH v2 2/4] app/test: refactor mod exp test case Arek Kusztal
2023-05-28 17:35 ` [PATCH v2 3/4] app/test: refactor mod inv tests Arek Kusztal
2023-05-28 17:35 ` [PATCH v2 4/4] app/test: add rsa kat and pwct tests Arek Kusztal
2023-05-30 10:48 ` Akhil Goyal [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=CO6PR18MB44848CFA258868AC3AEA140ED84B9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@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).