DPDK patches and discussions
 help / color / mirror / Atom feed
From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, kai.ji@intel.com, ciara.power@intel.com,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v3 0/3] Replace obsolote test cases.
Date: Mon, 19 Jun 2023 19:27:14 +0000	[thread overview]
Message-ID: <20230619192717.351336-1-arkadiuszx.kusztal@intel.com> (raw)

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 in the unit tests.
It frees particular alghorithm functions from any kind of responsibility to free resources for the new functions.

v2:
- fixed build problem with non compile-time constant
v3:
- rebased
- left old pwct tests intact

Arkadiusz Kusztal (3):
  app/test: remove obsolete test function
  app/test: add modexp and modinv functions
  app/test: add rsa none padding tests

 app/test/test_cryptodev_asym.c             | 761 +++++++++----------
 app/test/test_cryptodev_mod_test_vectors.h | 814 +--------------------
 app/test/test_cryptodev_rsa_test_vectors.h | 322 ++++----
 3 files changed, 510 insertions(+), 1387 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-06-19 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 19:27 Arek Kusztal [this message]
2023-06-19 19:27 ` [PATCH v3 1/3] app/test: remove obsolete test function Arek Kusztal
2023-06-19 19:27 ` [PATCH v3 2/3] app/test: add modexp and modinv functions Arek Kusztal
2023-06-19 19:27 ` [PATCH v3 3/3] app/test: add rsa none padding tests Arek Kusztal

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=20230619192717.351336-1-arkadiuszx.kusztal@intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --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).