DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Dooley, Brian" <brian.dooley@intel.com>,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: RE: [PATCH v2] examples/fips_validation: fix memory allocation in AES MCT test
Date: Fri, 7 Oct 2022 09:56:08 +0000	[thread overview]
Message-ID: <CO6PR18MB448487C76BFF3D46A38FCE8BD85F9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CY4PR11MB184876A9EA29E468FAFF86CC83519@CY4PR11MB1848.namprd11.prod.outlook.com>

> > Subject: [PATCH v2] examples/fips_validation: fix memory allocation in AES
> > MCT test
> >
> > Instead of allocating memory in every external iteration, do once in the
> > beginning of AES MCT tests and free at the end.
> >
> > Fixes: 8b8546aaedf ("examples/fips_validation: add parsing for AES-CBC")
> >
> > Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> > ---
> 
> Acked-by: Brian Dooley <brian.dooley@intel.com>
Applied to dpdk-next-crypto
Thanks.

      reply	other threads:[~2022-10-07  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13  6:44 [PATCH v1] examples/fips_validation: fix memory allocation in aes mct test Gowrishankar Muthukrishnan
2022-08-12 11:47 ` [PATCH v2] examples/fips_validation: fix memory allocation in AES MCT test Gowrishankar Muthukrishnan
2022-09-23 16:30   ` Dooley, Brian
2022-10-07  9:56     ` 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=CO6PR18MB448487C76BFF3D46A38FCE8BD85F9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=dev@dpdk.org \
    --cc=gmuthukrishn@marvell.com \
    --cc=roy.fan.zhang@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).