From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, roy.fan.zhang@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH] cryptodev: add support for 25519 and 448 curves
Date: Thu, 7 Apr 2022 14:43:34 +0100 [thread overview]
Message-ID: <20220407134334.20226-1-arkadiuszx.kusztal@intel.com> (raw)
This commit adds support for following elliptic curves:
1) Curve25519
2) Curve448
Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
---
lib/cryptodev/rte_crypto_asym.h | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
index cd24d4b07b..775b2f6277 100644
--- a/lib/cryptodev/rte_crypto_asym.h
+++ b/lib/cryptodev/rte_crypto_asym.h
@@ -48,6 +48,8 @@ enum rte_crypto_ec_group {
RTE_CRYPTO_EC_GROUP_SECP256R1 = 23,
RTE_CRYPTO_EC_GROUP_SECP384R1 = 24,
RTE_CRYPTO_EC_GROUP_SECP521R1 = 25,
+ RTE_CRYPTO_EC_GROUP_CURVE25519 = 29,
+ RTE_CRYPTO_EC_GROUP_CURVE448 = 30,
};
/**
@@ -180,9 +182,17 @@ typedef rte_crypto_param rte_crypto_uint;
*/
struct rte_crypto_ec_point {
rte_crypto_param x;
- /**< X coordinate */
+ /**<
+ * X coordinate
+ * For curve25519 and curve448 - little-endian integer
+ * otherwise, big-endian integer
+ */
rte_crypto_param y;
- /**< Y coordinate */
+ /**<
+ * Y coordinate
+ * For curve25519 and curve448 - little-endian integer
+ * otherwise, big-endian integer
+ */
};
/**
--
2.13.6
next reply other threads:[~2022-04-07 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 13:43 Arek Kusztal [this message]
2022-05-16 18:57 ` [EXT] " Akhil Goyal
2022-05-17 11:45 ` Kusztal, ArkadiuszX
2022-05-26 16:38 ` Akhil Goyal
2022-05-31 14:33 ` Kusztal, ArkadiuszX
2022-05-31 14:40 ` Akhil Goyal
2022-05-31 14:42 ` Kusztal, ArkadiuszX
2022-05-31 15:25 ` Akhil Goyal
2022-05-31 15:39 ` 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=20220407134334.20226-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=roy.fan.zhang@intel.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).