DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Dooley, Brian" <brian.dooley@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"gakhil@marvell.com" <gakhil@marvell.com>,
	 "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [PATCH v3 2/2] app/test: add SM4 GCM tests
Date: Tue, 18 Feb 2025 11:01:04 +0000	[thread overview]
Message-ID: <CO6PR11MB5587C483401784584A2B999984FA2@CO6PR11MB5587.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250113171022.1649181-2-brian.dooley@intel.com>

Hi Pablo,

> -----Original Message-----
> From: Dooley, Brian <brian.dooley@intel.com>
> Sent: Monday, January 13, 2025 6:10 PM
> Cc: dev@dpdk.org; gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; De Lara
> Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Dooley, Brian
> <brian.dooley@intel.com>
> Subject: [PATCH v3 2/2] app/test: add SM4 GCM tests
> 
> Added SM4-GCM tests for the AESNI MB PMD.
> 
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> ---
>  app/test/test_cryptodev.c                   | 158 +++++
>  app/test/test_cryptodev_aead_test_vectors.h | 708
> ++++++++++++++++++++
>  2 files changed, 866 insertions(+)
> 

Just one comment below.

Thanks,
Pablo
...

> b/app/test/test_cryptodev_aead_test_vectors.h
> index 73bfb8dad4..aacefe5ea4 100644
> --- a/app/test/test_cryptodev_aead_test_vectors.h
> +++ b/app/test/test_cryptodev_aead_test_vectors.h
> @@ -50,6 +50,54 @@ static uint8_t ccm_aad_test_2[22] = {
>  		0xA5, 0xB8, 0xFC, 0xBA, 0x00, 0x00
>  };
> 
> +static uint8_t sm4_gcm_aad_test_2[MAX_AAD_LENGTH] = {
> +		0x3f, 0x89, 0x42, 0x20
> +};

MAX_AAD_LENGTH is pretty much 64KB. This is allocating too much memory unnecessarily, so I would limit to the actual size .
You could use [] with no defined size, and that should work.
> +

...



  parent reply	other threads:[~2025-02-18 11:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 12:58 [PATCH v1 1/2] crypto/ipsec_mb: add SM4 GCM support Brian Dooley
2024-12-13 12:58 ` [PATCH v1 2/2] app/test: add SM4 GCM tests Brian Dooley
2025-01-13 16:39 ` [PATCH v2 1/2] crypto/ipsec_mb: add SM4 GCM support Brian Dooley
2025-01-13 16:39   ` Brian Dooley
2025-01-13 17:10 ` [PATCH v3 " Brian Dooley
2025-01-13 17:10   ` [PATCH v3 2/2] app/test: add SM4 GCM tests Brian Dooley
2025-01-29  9:32     ` Dooley, Brian
2025-02-18 11:01     ` De Lara Guarch, Pablo [this message]
2025-02-06 12:51   ` [EXTERNAL] [PATCH v3 1/2] crypto/ipsec_mb: add SM4 GCM support Akhil Goyal
2025-02-18 10:48   ` De Lara Guarch, Pablo
2025-02-19 11:49 ` [PATCH v4 1/3] " Brian Dooley
2025-02-19 11:50   ` [PATCH v4 2/3] cryptodev: add SM4 GCM Brian Dooley
2025-02-20 15:40     ` De Lara Guarch, Pablo
2025-02-19 11:50   ` [PATCH v4 3/3] app/test: add SM4 GCM tests Brian Dooley
2025-02-20 15:39   ` [PATCH v4 1/3] crypto/ipsec_mb: add SM4 GCM support De Lara Guarch, Pablo

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=CO6PR11MB5587C483401784584A2B999984FA2@CO6PR11MB5587.namprd11.prod.outlook.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=brian.dooley@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).