DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "brian.dooley@intel.com" <brian.dooley@intel.com>
Subject: RE: [EXTERNAL] [PATCH] app/test: refactor cryptodev test cases
Date: Tue, 1 Oct 2024 08:03:21 +0000	[thread overview]
Message-ID: <CO6PR18MB448490FAB39D321CD224F582D8772@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240925181525.66119-1-arkadiuszx.kusztal@intel.com>

> This commit introduces several changes to the cryptodev
> test cases that should make it easier to maintain.
> 
> Changes included in this patch:
> - If not needed by the specific test case, the device should be
> started/stopped in the particular testsuite setup/teardown
> function.
> - Most of the remaining test vectors were moved from test.c file
> to the specific header vector files.
> - Part of GCM redundant functions were replaced by named test cases.
> - Unit tests do not need to check for the symmetric cryptography feature,
> if this feature were not present, the test should not even reach this stage.
> 
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> ---
> Please note that this is work in progress, what is left to be done:
> - Rework security test cases, these will fail with current setup.
> - Fix OOP issue. OOP tests do not check for the prepended data in the OOP buffer.
> - Remove remaining test vectors from the .c file.
> - Remove redundant test functions that call common function, replace with
> named test cases.
> - Refactor block cipher functions, there are only three block cipher algorithms in
> the cryptodev.
> 
Nice work.

Please split the patch into smaller compiled patches.
It will be difficult to review such major changes in a single patch.


      parent reply	other threads:[~2024-10-01  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25 18:15 Arkadiusz Kusztal
2024-09-26 16:37 ` Patrick Robb
2024-10-01  8:03 ` 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=CO6PR18MB448490FAB39D321CD224F582D8772@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.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).