From: Shally Verma <shally.verma@caviumnetworks.com>
To: pablo.de.lara.guarch@intel.com
Cc: declan.doherty@intel.com, fiona.trahe@intel.com,
pathreya@caviumnetworks.com, ssahu@caviumnetworks.com,
agupta@caviumnetworks.com, dev@dpdk.org
Subject: [dpdk-dev] [PATCH v1 0/3]cryptodev: add unit tests and PMD for asym crypto
Date: Tue, 3 Apr 2018 16:01:06 +0530 [thread overview]
Message-ID: <1522751469-21307-1-git-send-email-shally.verma@caviumnetworks.com> (raw)
This patch series includes unit test, openssl pmd and documentation patches
for asymmetric crypto support in lib cryptodev framework.
These are based on asym patch V1 series
https://dpdk.org/dev/patchwork/patch/36575/
https://dpdk.org/dev/patchwork/patch/36576/
https://dpdk.org/dev/patchwork/patch/36577/
For API patch V1 summary
https://www.mail-archive.com/dev@dpdk.org/msg93657.html
Ashish Gupta (2):
lib/cryptodev: add unit testcase for asym crypto
doc: add asym crypto in cryptodev programmer guide
Shally Verma (1):
crypto/openssl: add asym crypto support
doc/guides/cryptodevs/features/openssl.ini | 11 +
doc/guides/cryptodevs/openssl.rst | 2 +
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 +
test/test/Makefile | 3 +-
test/test/test_cryptodev_asym.c | 1785 ++++++++++++++++++++++
8 files changed, 2923 insertions(+), 22 deletions(-)
create mode 100644 test/test/test_cryptodev_asym.c
--
2.14.3
next reply other threads:[~2018-04-03 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 10:31 Shally Verma [this message]
2018-04-03 10:31 ` [dpdk-dev] [PATCH v1 1/3] lib/cryptodev: add unit testcase " Shally Verma
2018-04-03 10:31 ` [dpdk-dev] [PATCH v1 2/3] crypto/openssl: add asym crypto support Shally Verma
2018-04-03 10:31 ` [dpdk-dev] [PATCH v1 3/3] doc: add asym crypto in cryptodev programmer guide 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=1522751469-21307-1-git-send-email-shally.verma@caviumnetworks.com \
--to=shally.verma@caviumnetworks.com \
--cc=agupta@caviumnetworks.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pathreya@caviumnetworks.com \
--cc=ssahu@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).