DPDK patches and discussions
 help / color / mirror / Atom feed
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 1/4] lib/cryptodev: add rsa priv key feature flag
Date: Thu, 28 Mar 2019 10:28:22 +0000	[thread overview]
Message-ID: <1553768834-19072-2-git-send-email-ayverma@marvell.com> (raw)
Message-ID: <20190328102822.MEvFyfeTm2vp6pQW9oRJ4daAY2H_L4q9TP-SVi5ICMc@z> (raw)
In-Reply-To: <1553768834-19072-1-git-send-email-ayverma@marvell.com>

Add feature flag to reflect RSA private key
operation support using quintuple (crt) or
exponent type key. if PMD support both,
then it should set both.

App should query cryptodev feature flag to check
if Sign and Decryt with CRT keys or exponent is
supported, thus call operation with relevant
key type.

Signed-off-by: Ayuj Verma <ayverma@marvell.com>
Signed-off-by: Shally Verma <shallyv@marvell.com>
---
 lib/librte_cryptodev/rte_cryptodev.c | 4 ++++
 lib/librte_cryptodev/rte_cryptodev.h | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/lib/librte_cryptodev/rte_cryptodev.c b/lib/librte_cryptodev/rte_cryptodev.c
index 871d7dd..cdc586a 100644
--- a/lib/librte_cryptodev/rte_cryptodev.c
+++ b/lib/librte_cryptodev/rte_cryptodev.c
@@ -486,6 +486,10 @@ struct rte_cryptodev_sym_session_pool_private_data {
 		return "CPU_ARM_CE";
 	case RTE_CRYPTODEV_FF_SECURITY:
 		return "SECURITY_PROTOCOL";
+	case RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_EXP:
+		return "RSA_PRIV_OP_KEY_EXP";
+	case RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_QT:
+		return "RSA_PRIV_OP_KEY_QT";
 	default:
 		return NULL;
 	}
diff --git a/lib/librte_cryptodev/rte_cryptodev.h b/lib/librte_cryptodev/rte_cryptodev.h
index a0bbcf9..298b352 100644
--- a/lib/librte_cryptodev/rte_cryptodev.h
+++ b/lib/librte_cryptodev/rte_cryptodev.h
@@ -438,6 +438,10 @@ struct rte_cryptodev_asym_capability_idx {
 /**< Utilises ARM CPU Cryptographic Extensions */
 #define	RTE_CRYPTODEV_FF_SECURITY			(1ULL << 16)
 /**< Support Security Protocol Processing */
+#define RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_EXP		(1ULL << 17)
+/**< Support RSA Private Key OP with exponent */
+#define RTE_CRYPTODEV_FF_RSA_PRIV_OP_KEY_QT		(1ULL << 18)
+/**< Support RSA Private Key OP with CRT (quintuple) Keys */
 
 
 /**
-- 
1.8.3.1


  parent reply	other threads:[~2019-03-28 10:28 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 " Ayuj Verma
2019-03-28 10:27 ` Ayuj Verma
2019-03-28 10:28 ` Ayuj Verma [this message]
2019-03-28 10:28   ` [dpdk-dev] [PATCH v3 1/4] lib/cryptodev: add " 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-2-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).