DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ashwin Sekhar Thalakalath Kottilveetil <asekhar@marvell.com>
To: "Ji, Kai" <kai.ji@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Akhil Goyal <gakhil@marvell.com>,
	Harman Kalra <hkalra@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
	Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
	Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	Satheesh Paul Antonysamy <psatheesh@marvell.com>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Koteswara Rao Kottidi <skoteshwar@marvell.com>
Subject: RE: [PATCH v4 0/1] crypto/openssl: add aes cmac support
Date: Mon, 18 Jul 2022 16:18:29 +0000	[thread overview]
Message-ID: <CO1PR18MB4540D348F3894289633CED9FBF8C9@CO1PR18MB4540.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN6PR11MB3408E190BADCE9667F81B84B818C9@SN6PR11MB3408.namprd11.prod.outlook.com>

Hi Kai,

Will fix the is duplication of OPENSSL_VERSION_NUMBER check.

Some CMAC tests are already present. The number of successful tests in cryptodev_openssl_autotest increases by 4 with this change. I am not planning to add more.

Regards,
Ashwin Sekhar T K 

> -----Original Message-----
> From: Ji, Kai <kai.ji@intel.com>
> Sent: Monday, July 18, 2022 7:27 PM
> To: Ashwin Sekhar Thalakalath Kottilveetil <asekhar@marvell.com>
> Cc: Anoob Joseph <anoobj@marvell.com>; dev@dpdk.org; Akhil Goyal
> <gakhil@marvell.com>; Harman Kalra <hkalra@marvell.com>; Jerin Jacob
> Kollanukkaran <jerinj@marvell.com>; Kiran Kumar Kokkilagadda
> <kirankumark@marvell.com>; Nithin Kumar Dabilpuram
> <ndabilpuram@marvell.com>; Pavan Nikhilesh Bhagavatula
> <pbhagavatula@marvell.com>; Satheesh Paul Antonysamy
> <psatheesh@marvell.com>; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> Sunil Kumar Kori <skori@marvell.com>; Satha Koteswara Rao Kottidi
> <skoteshwar@marvell.com>
> Subject: [EXT] RE: [PATCH v4 0/1] crypto/openssl: add aes cmac support
> 
> External Email
> 
> ----------------------------------------------------------------------
> Hi Ashwin,
> 
> There is duplication of OPENSSL_VERSION_NUMBER check in v4,  right
> before process_openssl_auth_mac().
> Are you planning to enable CMAC unit test case in
> cryptodev_openssl_autotest ?
> 
> Regards
> 
> Kai
> 
> 
> > -----Original Message-----
> > From: Ashwin Sekhar T K <asekhar@marvell.com>
> > Sent: Monday, July 18, 2022 10:19 AM
> > To: asekhar@marvell.com
> > Cc: anoobj@marvell.com; dev@dpdk.org; gakhil@marvell.com;
> > hkalra@marvell.com; jerinj@marvell.com; kirankumark@marvell.com;
> > ndabilpuram@marvell.com; pbhagavatula@marvell.com;
> > psatheesh@marvell.com; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> > skori@marvell.com; skoteshwar@marvell.com
> > Subject: [PATCH v4 0/1] crypto/openssl: add aes cmac support
> >
> > Add support for aes cmac operations.
> >
> > v2:
> >  * Added support for openssl 3.0
> > v3:
> >  * Fixed checkpatch warnings.
> > v4:
> >  * Fixed more checkpatch warnings.
> >
> > Ashwin Sekhar T K (1):
> >   crypto/openssl: support aes cmac operations
> >
> >  drivers/crypto/openssl/openssl_pmd_private.h |  14 ++
> >  drivers/crypto/openssl/rte_openssl_pmd.c     | 142
> ++++++++++++++++++-
> >  drivers/crypto/openssl/rte_openssl_pmd_ops.c |  20 +++
> >  3 files changed, 169 insertions(+), 7 deletions(-)
> >
> > --
> > 2.25.1


  reply	other threads:[~2022-07-18 16:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 16:28 [PATCH] crypto/openssl: support cmac operations Ashwin Sekhar T K
2022-06-17 10:11 ` Zhang, Roy Fan
2022-07-18  6:07   ` [PATCH v2 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18  6:07     ` [PATCH v2 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18  9:12       ` [PATCH v3 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18  9:12         ` [PATCH v3 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18  9:18           ` [PATCH v4 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18  9:18             ` [PATCH v4 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18 16:25               ` [PATCH v5 0/1] crypto/openssl: add aes cmac support Ashwin Sekhar T K
2022-07-18 16:25                 ` [PATCH v5 1/1] crypto/openssl: support aes cmac operations Ashwin Sekhar T K
2022-07-18 16:54                   ` Ji, Kai
2022-08-26  8:52                     ` Akhil Goyal
2022-07-18 13:57             ` [PATCH v4 0/1] crypto/openssl: add aes cmac support Ji, Kai
2022-07-18 16:18               ` Ashwin Sekhar Thalakalath Kottilveetil [this message]
2022-06-30 15:41 ` [PATCH v2] crypto/ipsec_mb: enable support for arm64 Ashwin Sekhar T K
2022-07-04 14:47   ` Zhang, Roy Fan
2022-07-27  8:29   ` Ruifeng Wang
2022-07-27  8:48     ` Ashwin Sekhar Thalakalath Kottilveetil
2022-08-26  8:45     ` Akhil Goyal

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=CO1PR18MB4540D348F3894289633CED9FBF8C9@CO1PR18MB4540.namprd18.prod.outlook.com \
    --to=asekhar@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=hkalra@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=psatheesh@marvell.com \
    --cc=roy.fan.zhang@intel.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@marvell.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).