DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Verma, Shally" <Shally.Verma@cavium.com>
To: "Verma, Shally" <Shally.Verma@cavium.com>,
	"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>
Cc: "declan.doherty@intel.com" <declan.doherty@intel.com>,
	"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
	"Athreya, Narayana Prasad" <NarayanaPrasad.Athreya@cavium.com>,
	"Sahu, Sunila" <Sunila.Sahu@cavium.com>,
	 "Gupta, Ashish" <Ashish.Gupta@cavium.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Murthy, Nidadavolu" <Nidadavolu.Murthy@cavium.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/6] crypto: add asym crypto support
Date: Fri, 20 Apr 2018 06:16:53 +0000	[thread overview]
Message-ID: <CY4PR0701MB3634DBC42E2794652FA43D0EF0B40@CY4PR0701MB3634.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1522927489-23668-1-git-send-email-shally.verma@caviumnetworks.com>

Ping. 
Could you please review and provide feedback.

Thanks
Shally

>-----Original Message-----
>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shally Verma
>Sent: 05 April 2018 16:55
>To: pablo.de.lara.guarch@intel.com
>Cc: declan.doherty@intel.com; fiona.trahe@intel.com; Athreya, Narayana Prasad <NarayanaPrasad.Athreya@cavium.com>; Sahu,
>Sunila <Sunila.Sahu@cavium.com>; Gupta, Ashish <Ashish.Gupta@cavium.com>; dev@dpdk.org
>Subject: [dpdk-dev] [PATCH v2 0/6] crypto: add asym crypto support
>
>This patch series add support for asymmetric crypto in DPDK
>librte_cryptodev framework along with unit test, PMD and
>documentation updates and addresses patch apply failure
>raised on asym crypto v1 patch series:
>https://dpdk.org/dev/patchwork/patch/36575/
>https://dpdk.org/dev/patchwork/patch/36576/
>https://dpdk.org/dev/patchwork/patch/36577/
>
>And, unit test and PMD patch series:
>https://dpdk.org/dev/patchwork/patch/36928/
>https://dpdk.org/dev/patchwork/patch/36929/
>https://dpdk.org/dev/patchwork/patch/36930/
>
>Key changes from PATCH v1:
>- resolve git apply patch error on patch id 36575
>- resolve git apply patch error on patch id 36929
>
>Key changes from RFCv1 include:
>- removal of dedicated sym and asym qp setup,
>- remove asym qp count and attach/detach_session apis
>- re-org xforms params for deffie-hellman to allow
>  public key and optional private key generations
>- move elliptic curve changes into another separate patch/patch series
>
>This patch series is divided in to following categories:
>1. library patches with asymmetric API, xform and capability
>   definitions
>2. Unit test case addition
>3. Openssl PMD changes with asymmetric crypto support
>4. Programmer Guide updates with asymmetric description
>
>TBD:
>- add elliptic curve support
>- rename of existing session_configure/clear APIs to
>  sym_session_configure/clear/init APIs
>
>It is based on review discussion on RFC v1 asym crypto patch
>http://dpdk.org/patch/34308.
>
>RFC v1 patch http://dpdk.org/patch/34308 is further a derivative of
>earlier reviewed  RFC v2 patch series:
> http://dpdk.org/dev/patchwork/patch/24245/
> http://dpdk.org/dev/patchwork/patch/24246/
> http://dpdk.org/dev/patchwork/patch/24247/
>
>Shally Verma (6):
>  lib/cryptodev: add asymmetric algos in cryptodev
>  lib/cryptodev: add asym op support in cryptodev
>  lib/cryptodev: add asymmetric crypto capability in cryptodev
>  test/crypto: add unit testcase for asym crypto
>  crypto/openssl: add asym crypto support
>  doc: add asym crypto in cryptodev programmer guide
>
> doc/guides/cryptodevs/features/openssl.ini       |   11 +
> doc/guides/cryptodevs/openssl.rst                |    1 +
> doc/guides/prog_guide/cryptodev_lib.rst          |  338 +++-
> drivers/crypto/openssl/rte_openssl_pmd.c         |  377 ++++-
> drivers/crypto/openssl/rte_openssl_pmd_ops.c     |  400 ++++-
> drivers/crypto/openssl/rte_openssl_pmd_private.h |   29 +
> lib/librte_cryptodev/Makefile                    |    3 +-
> lib/librte_cryptodev/rte_crypto.h                |   37 +-
> lib/librte_cryptodev/rte_crypto_asym.h           |  519 +++++++
> lib/librte_cryptodev/rte_cryptodev.c             |  218 ++-
> lib/librte_cryptodev/rte_cryptodev.h             |  186 ++-
> lib/librte_cryptodev/rte_cryptodev_pmd.h         |   58 +-
> lib/librte_cryptodev/rte_cryptodev_version.map   |   16 +
> test/test/Makefile                               |    3 +-
> test/test/test_cryptodev_asym.c                  | 1785 ++++++++++++++++++++++
> 15 files changed, 3952 insertions(+), 29 deletions(-)
> create mode 100644 lib/librte_cryptodev/rte_crypto_asym.h
> create mode 100644 test/test/test_cryptodev_asym.c
>
>--
>1.9.1

      parent reply	other threads:[~2018-04-20  6:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 11:24 Shally Verma
2018-04-05 11:24 ` [dpdk-dev] [PATCH v2 1/6] lib/cryptodev: add asymmetric algos in cryptodev Shally Verma
2018-05-08 15:08   ` Trahe, Fiona
2018-04-05 11:24 ` [dpdk-dev] [PATCH v2 2/6] lib/cryptodev: add asym op support " Shally Verma
2018-05-08 10:51   ` Trahe, Fiona
2018-05-08 10:58     ` Verma, Shally
2018-05-08 18:32       ` De Lara Guarch, Pablo
2018-05-08 14:43   ` Trahe, Fiona
2018-05-09  7:33     ` Verma, Shally
2018-04-05 11:24 ` [dpdk-dev] [PATCH v2 3/6] lib/cryptodev: add asymmetric crypto capability " Shally Verma
2018-05-08 15:00   ` Trahe, Fiona
2018-05-09  7:34     ` Verma, Shally
2018-04-05 11:24 ` [dpdk-dev] [PATCH v2 4/6] test/crypto: add unit testcase for asym crypto Shally Verma
2018-04-05 11:24 ` [dpdk-dev] [PATCH v2 5/6] crypto/openssl: add asym crypto support Shally Verma
2018-05-09 10:33   ` Trahe, Fiona
2018-05-09 10:56     ` Verma, Shally
2018-04-05 11:24 ` [dpdk-dev] [PATCH v2 6/6] doc: add asym crypto in cryptodev programmer guide Shally Verma
2018-04-11 12:37 ` [dpdk-dev] [PATCH v2 0/6] crypto: add asym crypto support De Lara Guarch, Pablo
2018-04-11 14:14   ` Verma, Shally
2018-04-20  6:16 ` Verma, Shally [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=CY4PR0701MB3634DBC42E2794652FA43D0EF0B40@CY4PR0701MB3634.namprd07.prod.outlook.com \
    --to=shally.verma@cavium.com \
    --cc=Ashish.Gupta@cavium.com \
    --cc=NarayanaPrasad.Athreya@cavium.com \
    --cc=Nidadavolu.Murthy@cavium.com \
    --cc=Sunila.Sahu@cavium.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pablo.de.lara.guarch@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).