DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ayuj Verma <ayverma@marvell.com>
To: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>, Shally Verma <shallyv@marvell.com>,
	Sunila Sahu <ssahu@marvell.com>,
	Kanaka Durga Kotamarthy <kkotamarthy@marvell.com>,
	Arvind Desai <adesai@marvell.com>,
	Ayuj Verma <ayverma@marvell.com>
Subject: [dpdk-dev] [PATCH 1/3] lib/cryptodev: add crt sign and decrypt ops
Date: Wed, 6 Feb 2019 11:16:29 +0000	[thread overview]
Message-ID: <20190206111405.30860-2-ayverma@marvell.com> (raw)
In-Reply-To: <20190206111405.30860-1-ayverma@marvell.com>

Add CRT variant of RTE_CRYPTO_ASYM_SIGN and DECRYPT operation,
to perform RSA Sign and Decrypt using CRT quintuple keys only

PMD would reflect its capability to support these
operations using its op_type mask. App should query
RSA xform capability API to check if specific op_type 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_crypto_asym.h | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/lib/librte_cryptodev/rte_crypto_asym.h b/lib/librte_cryptodev/rte_crypto_asym.h
index 5e185b2dd..2c1f95eb6 100644
--- a/lib/librte_cryptodev/rte_crypto_asym.h
+++ b/lib/librte_cryptodev/rte_crypto_asym.h
@@ -91,8 +91,16 @@ enum rte_crypto_asym_op_type {
 	/**< Asymmetric Encrypt operation */
 	RTE_CRYPTO_ASYM_OP_DECRYPT,
 	/**< Asymmetric Decrypt operation */
+	RTE_CRYPTO_ASYM_OP_DECRYPT_CRT,
+	/**< RSA private key decrypt operation
+	 * using CRT quintuple keys
+	 */
 	RTE_CRYPTO_ASYM_OP_SIGN,
 	/**< Signature Generation operation */
+	RTE_CRYPTO_ASYM_OP_SIGN_CRT,
+	/**< RSA signature (private key encrypt)
+	 * generation using CRT quintuple keys
+	 */
 	RTE_CRYPTO_ASYM_OP_VERIFY,
 	/**< Signature Verification operation */
 	RTE_CRYPTO_ASYM_OP_PRIVATE_KEY_GENERATE,
-- 
2.20.0

  reply	other threads:[~2019-02-06 11:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 11:16 [dpdk-dev] [PATCH 0/3] adding op-type crt sign and decrypt Ayuj Verma
2019-02-06 11:16 ` Ayuj Verma [this message]
2019-02-06 11:16 ` [dpdk-dev] [PATCH 2/3] crypto/openssl: update op-type mask with crt ops Ayuj Verma
2019-02-06 11:16 ` [dpdk-dev] [PATCH 3/3] test/crypto: check for rsa capa for op-type Ayuj Verma
2019-02-08  8:47 ` [dpdk-dev] [PATCH 0/3] adding op-type crt sign and decrypt Ayuj Verma
     [not found]   ` <348A99DA5F5B7549AA880327E580B435896EBE65@IRSMSX101.ger.corp.intel.com>
     [not found]     ` <DM6PR18MB29087B09817C8ABDF820CDE0AD640@DM6PR18MB2908.namprd18.prod.outlook.com>
     [not found]       ` <06EE24DD0B19E248B53F6DC8657831551B13B064@hasmsx109.ger.corp.intel.com>
2019-02-12  5:27         ` Shally Verma
2019-02-12 11:12           ` Kusztal, ArkadiuszX
2019-02-12 11:19             ` Shally Verma
2019-02-12 11:36               ` Kusztal, ArkadiuszX

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=20190206111405.30860-2-ayverma@marvell.com \
    --to=ayverma@marvell.com \
    --cc=adesai@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=kkotamarthy@marvell.com \
    --cc=pablo.de.lara.guarch@intel.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).