From: Shally Verma <shally.verma@caviumnetworks.com>
To: declan.doherty@intel.com
Cc: dev@dpdk.org, pathreya@caviumnetworks.com,
nmurthy@caviumnetworks.com, ssahu@caviumnetworks.com,
agupta@caviumnetworks.com
Subject: [dpdk-dev] [RFC v1 0/1] lib/cryptodev: add support of asymmetric crypto
Date: Tue, 23 Jan 2018 15:24:22 +0530 [thread overview]
Message-ID: <1516701263-13154-1-git-send-email-shally.verma@caviumnetworks.com> (raw)
This an RFC API specification to add support for asymmetric crypto
in DPDK cryptodev library. It is derivative of earlier submitted
RFC v2 patch series by Umesh Kartha (umesh.kartha@caviumnetworks.com):
http://dpdk.org/dev/patchwork/patch/24245/
http://dpdk.org/dev/patchwork/patch/24246/
http://dpdk.org/dev/patchwork/patch/24247/
and *inclusive of review comments on RFC v2* with few minor changes
to asymmetric xform structures. Current list of proposed asymmetric
algorithm is as per RFC v2.
This spec primarily addresses last open review comment regarding
queue pair management among different kind of crypto devices.
Since, crypto devices can be of different capabilities, such as:
- can perform symmetric only operations,
- can perform asymmetric only operations,
- can do both but may have different ways to manage queue pairs, such
as, may have dedicated queues for these or may use all qp to input
any kind of operation.
Thus, it become key design question how to enable PMDs to do crypto
operations with such different capabilities and queue arrangements.
So, current specification focuses on defining device capabilities
and PMD operations so as to encompass all kind of anticipated crypto
devices and intend to invite discussions and feedback on same.
Current version only complete with RSA algorithm and associated params.
Others algorithm capability and params will be added subsequently.
Shally Verma (1):
lib/cryptodev: add support of asymmetric crypto
lib/librte_cryptodev/Makefile | 1 +
lib/librte_cryptodev/rte_crypto.h | 39 +-
lib/librte_cryptodev/rte_crypto_asym.h | 949 +++++++++++++++++++++++++
lib/librte_cryptodev/rte_cryptodev.c | 287 ++++++++
lib/librte_cryptodev/rte_cryptodev.h | 358 +++++++++-
lib/librte_cryptodev/rte_cryptodev_pmd.c | 19 +-
lib/librte_cryptodev/rte_cryptodev_pmd.h | 154 +++-
lib/librte_cryptodev/rte_cryptodev_version.map | 21 +
8 files changed, 1811 insertions(+), 17 deletions(-)
create mode 100644 lib/librte_cryptodev/rte_crypto_asym.h
--
1.9.1
next reply other threads:[~2018-01-23 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 9:54 Shally Verma [this message]
2018-01-23 9:54 ` [dpdk-dev] [RFC v1 1/1] " Shally Verma
2018-02-01 11:36 ` [dpdk-dev] FW: " Verma, Shally
2018-02-02 15:12 ` Jain, Deepak K
2018-02-09 18:13 ` [dpdk-dev] " Trahe, Fiona
2018-02-15 5:32 ` Verma, Shally
2018-02-15 11:46 ` Trahe, Fiona
2018-02-22 5:50 ` Verma, Shally
2018-02-22 10:38 ` Trahe, Fiona
2018-03-07 12:16 ` Verma, Shally
2018-03-14 12:12 ` Trahe, Fiona
2018-03-16 8:02 ` Verma, Shally
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=1516701263-13154-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=nmurthy@caviumnetworks.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).