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] lib/cryptodev: add support of asymmetric crypto
Date: Tue, 27 Mar 2018 18:24:38 +0530 [thread overview]
Message-ID: <1522155281-16329-1-git-send-email-shally.verma@caviumnetworks.com> (raw)
This patch series add support for asymmetric crypto API specification
in DPDK librte_cryptodev library.
It is based on review discussion on RFC v1 patch
http://dpdk.org/patch/34308
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
Todo:
- add elliptic curve support
- rename of existing session_configure/clear APIs to
sym_session_configure/clear/init APIs
This patch series is divided in to 3 patches:
1. lib/cryptodev: add support for asymmetric crypto op in cryptodev
Extend librte_cryptodev for asymmetric op pool and sessions
create/destroy and other associated PMD ops
2. lib/cryptodev: add asymmetric crypto capability in cryptodev
Extend capability in librte_cryptodev for asymmetric capability
and associated APIs
3. lib/cryptodev: add asymmetric algos in cryptodev
Add new rte_crypto_asym.h defining supported asymmetric
algos(xforms) and associated ops structures
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 (3):
lib/cryptodev: add support for asymmetric crypto op
lib/cryptodev: add asymmetric crypto capability in cryptodev
lib/cryptodev: add asymmetric algos in cryptodev
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 | 17 +
7 files changed, 1031 insertions(+), 7 deletions(-)
create mode 100644 lib/librte_cryptodev/rte_crypto_asym.h
--
2.14.3
next reply other threads:[~2018-03-27 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 12:54 Shally Verma [this message]
2018-03-27 12:54 ` [dpdk-dev] [PATCH v1 1/3] lib/cryptodev: add support for asymmetric crypto op Shally Verma
2018-03-27 12:54 ` [dpdk-dev] [PATCH v1 2/3] lib/cryptodev: add asymmetric crypto capability in cryptodev Shally Verma
2018-03-27 12:54 ` [dpdk-dev] [PATCH v1 3/3] lib/cryptodev: add asymmetric algos " 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=1522155281-16329-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).