DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shally Verma <shally.verma@caviumnetworks.com>
To: pablo.de.lara.guarch@intel.com
Cc: dev@dpdk.org, pathreya@caviumnetworks.com, nmurthy@caviumnetworks.com
Subject: [dpdk-dev] [PATCH v4 0/3]crypto/openssl: support asymmetric crypto
Date: Thu, 12 Jul 2018 19:38:43 +0530	[thread overview]
Message-ID: <1531404526-17984-1-git-send-email-shally.verma@caviumnetworks.com> (raw)

This patch series add asymmetric crypto support in openssl pmd
changes in v4:
- add openssl 1.1.0h support in openssl PMD for asym operations.
- A compat.h added for PMD compatibility with both 1.0.2 and 1.1.0
- update openssl document with asymmetric feature support 

For further history refer https://patches.dpdk.org/patch/40079/

Sunila Sahu (3):
  crypto/openssl: add rsa and mod asym op
  crypto/openssl: add dh and dsa asym op
  doc: add asym feature list

 doc/guides/cryptodevs/features/openssl.ini       |  11 +
 doc/guides/cryptodevs/openssl.rst                |   1 +
 drivers/crypto/openssl/compat.h                  | 108 +++++
 drivers/crypto/openssl/rte_openssl_pmd.c         | 466 +++++++++++++++++++-
 drivers/crypto/openssl/rte_openssl_pmd_ops.c     | 528 ++++++++++++++++++++++-
 drivers/crypto/openssl/rte_openssl_pmd_private.h |  28 ++
 6 files changed, 1130 insertions(+), 12 deletions(-)
 create mode 100644 drivers/crypto/openssl/compat.h

-- 
2.9.5

             reply	other threads:[~2018-07-12 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 14:08 Shally Verma [this message]
2018-07-12 14:08 ` [dpdk-dev] [PATCH v4 1/3] crypto/openssl: add rsa and mod asym op Shally Verma
2018-07-23 12:32   ` De Lara Guarch, Pablo
2018-07-12 14:08 ` [dpdk-dev] [PATCH v4 2/3] crypto/openssl: add dh and dsa " Shally Verma
2018-07-12 14:08 ` [dpdk-dev] [PATCH v4 3/3] doc: add asym feature list Shally Verma

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=1531404526-17984-1-git-send-email-shally.verma@caviumnetworks.com \
    --to=shally.verma@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=nmurthy@caviumnetworks.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=pathreya@caviumnetworks.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).