DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
	"O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] test/crypto: Add AES-256 DOCSIS test	vectors
Date: Mon, 16 Mar 2020 17:39:45 +0000	[thread overview]
Message-ID: <SN6PR11MB2847E93E368A8EB39D191A6884F90@SN6PR11MB2847.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BN6PR11MB1796B6E8C65DF1C31F49B529E4E50@BN6PR11MB1796.namprd11.prod.outlook.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Trahe, Fiona
> Sent: Wednesday, March 4, 2020 1:40 PM
> To: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>; akhil.goyal@nxp.com
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 2/2] test/crypto: Add AES-256 DOCSIS test
> vectors
> 
> Hi Máirtin,
> Wasn't this patch already upstreamed with the QAT patchset?
> If so no need to resend.

Actually, I think this patch (or the one in QAT) requires an important change.
If a device doesn't support 32-byte keys, these test cases will fail, so you need
to retrieve the capabilities of the device and check if it supports the key size.

Thanks,
Pablo

> Fiona
> 
> > -----Original Message-----
> > From: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> > Sent: Wednesday, March 4, 2020 9:18 AM
> > To: Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com
> > Cc: dev@dpdk.org; O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> > Subject: [PATCH 2/2] test/crypto: Add AES-256 DOCSIS test vectors
> >
> > This patch adds test vectors for AES-256 and sets AESNI-MB as the
> > target PMD
> >
> > Signed-off-by: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
> > ---
> >  app/test/test_cryptodev_aes_test_vectors.h |  176
> > ++++++++++++++++++++++++++++
> >  1 files changed, 176 insertions(+), 0 deletions(-)
> >


  reply	other threads:[~2020-03-16 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  9:17 [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: support DOCSIS AES-256 Mairtin o Loingsigh
2020-03-04  9:17 ` [dpdk-dev] [PATCH 2/2] test/crypto: Add AES-256 DOCSIS test vectors Mairtin o Loingsigh
2020-03-04 13:39   ` Trahe, Fiona
2020-03-16 17:39     ` De Lara Guarch, Pablo [this message]
2020-03-04  9:25 [dpdk-dev] [PATCH 1/2] crypto/aesni_mb: support DOCSIS AES-256 Mairtin o Loingsigh
2020-03-04  9:25 ` [dpdk-dev] [PATCH 2/2] test/crypto: Add AES-256 DOCSIS test vectors Mairtin o Loingsigh

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=SN6PR11MB2847E93E368A8EB39D191A6884F90@SN6PR11MB2847.namprd11.prod.outlook.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=mairtin.oloingsigh@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).