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 0/4] adding rsa priv key feature flag
Date: Thu, 28 Mar 2019 10:27:52 +0000 [thread overview]
Message-ID: <1553768834-19072-1-git-send-email-ayverma@marvell.com> (raw)
Some PMDs can support RSA private key operations using CRT
(quintuple) or exponent key only. Thus add a feature flag
RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_EXP and
RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_QT in PMD to reflect which key
type is supported to perform rsa private key op.
App should query PMD feature flag to check if specific
key type is supported and call operation with relevant key type.
Changes in v3:
- Rebase changes on top of latest unit test application
- add feature flag description in documentation
Changes in v2:
- RSA key type feature flags exponenet and quintuple,
in place of making them part of xform capabilities.
Ayuj Verma (4):
lib/cryptodev: add rsa priv key feature flag
crypto/openssl: set rsa private op feature flag
app/test: check for key type ff in asym unit test
doc: add rsa key type to feature list
app/test/test_cryptodev_asym.c | 26 ++++++++++++++++++++++++++
doc/guides/cryptodevs/features/openssl.ini | 2 ++
doc/guides/cryptodevs/overview.rst | 6 ++++++
drivers/crypto/openssl/rte_openssl_pmd.c | 4 +++-
lib/librte_cryptodev/rte_cryptodev.c | 4 ++++
lib/librte_cryptodev/rte_cryptodev.h | 4 ++++
6 files changed, 45 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2019-03-28 10:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 10:27 Ayuj Verma [this message]
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 ` [dpdk-dev] [PATCH v3 4/4] doc: add rsa key type to feature list Ayuj Verma
2019-03-28 10:28 ` 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-1-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).