From: Ayuj Verma <ayverma@marvell.com>
To: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
"Shally Verma" <shallyv@marvell.com>,
Sunila Sahu <ssahu@marvell.com>,
"Kanaka Durga Kotamarthy" <kkotamarthy@marvell.com>,
Arvind Desai <adesai@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>,
Ayuj Verma <ayverma@marvell.com>
Subject: [dpdk-dev] [PATCH v3 4/4] doc: add rsa key type to feature list
Date: Thu, 28 Mar 2019 10:28:56 +0000 [thread overview]
Message-ID: <1553768834-19072-5-git-send-email-ayverma@marvell.com> (raw)
In-Reply-To: <1553768834-19072-1-git-send-email-ayverma@marvell.com>
Add ff description in overview.rst and update
feature support in Openssl PMD feature list
Signed-off-by: Ayuj Verma <ayverma@marvell.com>
Signed-off-by: Shally Verma <shallyv@marvell.com>
---
doc/guides/cryptodevs/features/openssl.ini | 2 ++
doc/guides/cryptodevs/overview.rst | 6 ++++++
2 files changed, 8 insertions(+)
diff --git a/doc/guides/cryptodevs/features/openssl.ini b/doc/guides/cryptodevs/features/openssl.ini
index b9c0bdc..6ddca39 100644
--- a/doc/guides/cryptodevs/features/openssl.ini
+++ b/doc/guides/cryptodevs/features/openssl.ini
@@ -9,6 +9,8 @@ Sym operation chaining = Y
OOP SGL In LB Out = Y
OOP LB In LB Out = Y
Asymmetric crypto = Y
+RSA PRIV OP KEY EXP = Y
+RSA PRIV OP KEY QT = Y
;
; Supported crypto algorithms of the 'openssl' crypto driver.
diff --git a/doc/guides/cryptodevs/overview.rst b/doc/guides/cryptodevs/overview.rst
index 607e758..d7b7141 100644
--- a/doc/guides/cryptodevs/overview.rst
+++ b/doc/guides/cryptodevs/overview.rst
@@ -37,6 +37,12 @@ Supported Feature Flags
which means that Out-of-place operation is supported,
with linear input and output buffers.
+ - "RSA PRIV OP KEY EXP" feature flag means PMD support RSA private key
+ operation (Sign and Decrypt) using exponent key type only.
+
+ - "RSA PRIV OP KEY QT" feature flag means PMD support RSA private key
+ operation (Sign and Decrypt) using quintuple (crt) type key only.
+
Supported Cipher Algorithms
---------------------------
--
1.8.3.1
next prev parent reply other threads:[~2019-03-28 10:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 10:27 [dpdk-dev] [PATCH v3 0/4] adding rsa priv key feature flag Ayuj Verma
2019-03-28 10:27 ` Ayuj Verma
2019-03-28 10:28 ` [dpdk-dev] [PATCH v3 1/4] lib/cryptodev: add " Ayuj Verma
2019-03-28 10:28 ` Ayuj Verma
2019-03-28 10:28 ` [dpdk-dev] [PATCH v3 2/4] crypto/openssl: set rsa private op " Ayuj Verma
2019-03-28 10:28 ` Ayuj Verma
2019-03-28 10:28 ` [dpdk-dev] [PATCH v3 3/4] app/test: check for key type ff in asym unit test Ayuj Verma
2019-03-28 10:28 ` Ayuj Verma
2019-03-28 10:28 ` Ayuj Verma [this message]
2019-03-28 10:28 ` [dpdk-dev] [PATCH v3 4/4] doc: add rsa key type to feature list Ayuj Verma
2019-03-29 15:01 ` [dpdk-dev] [PATCH v3 0/4] adding rsa priv key feature flag Akhil Goyal
2019-03-29 15:01 ` Akhil Goyal
2019-03-29 15:17 ` Akhil Goyal
2019-03-29 15:17 ` Akhil Goyal
2019-03-29 15:20 ` Ayuj Verma
2019-03-29 15:20 ` Ayuj Verma
2019-04-03 8:47 ` Akhil Goyal
2019-04-03 8:47 ` Akhil Goyal
2019-04-03 10:09 ` Ayuj Verma
2019-04-03 10:09 ` Ayuj 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=1553768834-19072-5-git-send-email-ayverma@marvell.com \
--to=ayverma@marvell.com \
--cc=adesai@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=kkotamarthy@marvell.com \
--cc=shallyv@marvell.com \
--cc=ssahu@marvell.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).