DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tejasree Kondoj <ktejasree@marvell.com>
To: Tejasree Kondoj <ktejasree@marvell.com>,
	Akhil Goyal <akhil.goyal@nxp.com>,
	Radu Nicolau <radu.nicolau@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
	Ankur Dwivedi <adwivedi@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/2] support SSL/TLS way of cipher-auth operations
Date: Thu, 21 Jan 2021 07:26:50 +0000	[thread overview]
Message-ID: <PH0PR18MB3864C3281D4601BB4898A853A8A19@PH0PR18MB3864.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20201218141016.1834-1-ktejasree@marvell.com>

Hi Akhil,

I'm planning to add device feature flag(RTE_CRYPTODEV_FF_SSL_ORDER) 
along with SSL test cases movement to chain array in v2. Would that be fine?
Feature flag is needed to skip SSL test cases if device doesn't support them.

Thanks
Tejasree

> -----Original Message-----
> From: Tejasree Kondoj <ktejasree@marvell.com>
> Sent: Friday, December 18, 2020 7:40 PM
> To: Akhil Goyal <akhil.goyal@nxp.com>; Radu Nicolau
> <radu.nicolau@intel.com>
> Cc: Tejasree Kondoj <ktejasree@marvell.com>; Anoob Joseph
> <anoobj@marvell.com>; Ankur Dwivedi <adwivedi@marvell.com>;
> dev@dpdk.org
> Subject: [PATCH 0/2] support SSL/TLS way of cipher-auth operations
> 
> This series adds SSL/TLS way of cipher-auth operations support i.e. auth
> generation followed by encryption and decryption followed by auth verify in
> OCTEON TX, OCTEON TX2 PMDs and sample unit test application.
> 
> Tejasree Kondoj (2):
>   common/cpt: support SSL/TLS way of cipher-auth operations
>   test/crypto: support SSL/TLS way of cipher-auth operations
> 
>  app/test/test_cryptodev_aes_test_vectors.h    | 576 ++++++++++++++++++
>  app/test/test_cryptodev_blockcipher.c         |  98 ++-
>  app/test/test_cryptodev_blockcipher.h         |   9 +
>  doc/guides/rel_notes/release_21_02.rst        |  12 +
>  drivers/common/cpt/cpt_mcode_defines.h        |   7 +-
>  drivers/common/cpt/cpt_ucode.h                |  42 +-
>  drivers/crypto/octeontx/otx_cryptodev_ops.c   |   8 +-
>  drivers/crypto/octeontx2/otx2_cryptodev_ops.c |   8 +-
>  8 files changed, 736 insertions(+), 24 deletions(-)
> 
> --
> 2.27.0


  parent reply	other threads:[~2021-01-21  7:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 14:10 Tejasree Kondoj
2020-12-18 14:10 ` [dpdk-dev] [PATCH 1/2] common/cpt: " Tejasree Kondoj
2020-12-18 14:10 ` [dpdk-dev] [PATCH 2/2] test/crypto: " Tejasree Kondoj
2021-01-19 17:00   ` Akhil Goyal
2021-01-19 18:02     ` Doherty, Declan
2021-01-20 12:51     ` Zhang, Roy Fan
2021-01-20 14:34     ` Zhang, Roy Fan
2021-01-20 14:40       ` Tejasree Kondoj
2021-01-21  9:26   ` Kusztal, ArkadiuszX
2021-01-21 10:02     ` Tejasree Kondoj
2021-01-15  5:31 ` [dpdk-dev] [PATCH 0/2] " Anoob Joseph
2021-01-21  7:26 ` Tejasree Kondoj [this message]
2021-01-25 16:56   ` Akhil Goyal
2021-01-27 12:00     ` Tejasree Kondoj

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=PH0PR18MB3864C3281D4601BB4898A853A8A19@PH0PR18MB3864.namprd18.prod.outlook.com \
    --to=ktejasree@marvell.com \
    --cc=adwivedi@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=radu.nicolau@intel.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).