From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>
Cc: Anoob Joseph <anoobj@marvell.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
Brian Dooley <brian.dooley@intel.com>,
Akhil Goyal <gakhil@marvell.com>, <jerinj@marvell.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>
Subject: [v1 1/2] cryptodev: add enumeration in EC xform for FPM
Date: Tue, 27 Sep 2022 13:00:42 +0530 [thread overview]
Message-ID: <f1e5d19fa3da1accc14dc52c770642e9faa17f90.1664262839.git.gmuthukrishn@marvell.com> (raw)
In-Reply-To: <cover.1664262839.git.gmuthukrishn@marvell.com>
Add enumeration in EC xform for FPM. Crypto driver would need this
to xform point multiplication based on given type of EC curve.
Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
---
lib/cryptodev/rte_crypto_asym.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
index 8ae43d5f3d..da13a5e0c1 100644
--- a/lib/cryptodev/rte_crypto_asym.h
+++ b/lib/cryptodev/rte_crypto_asym.h
@@ -116,6 +116,9 @@ enum rte_crypto_asym_xform_type {
/**< Elliptic Curve Diffie Hellman */
RTE_CRYPTO_ASYM_XFORM_ECPM,
/**< Elliptic Curve Point Multiplication */
+
+ RTE_CRYPTO_ASYM_XFORM_ECFPM,
+ /**< Elliptic Curve Fixed Point Multiplication */
RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END
/**< End of list */
};
--
2.25.1
next prev parent reply other threads:[~2022-09-27 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 7:30 [v1 0/2] examples/fips_validation: add ECDSA tests Gowrishankar Muthukrishnan
2022-09-27 7:30 ` Gowrishankar Muthukrishnan [this message]
2022-09-28 21:35 ` [v1 1/2] cryptodev: add enumeration in EC xform for FPM Ji, Kai
2022-09-30 18:08 ` Akhil Goyal
2022-09-27 7:30 ` [v1 2/2] examples/fips_validation: add ECDSA validation Gowrishankar Muthukrishnan
2022-10-07 10:50 ` Akhil Goyal
2022-10-17 9:34 ` Dooley, Brian
2022-10-21 15:48 ` Akhil Goyal
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=f1e5d19fa3da1accc14dc52c770642e9faa17f90.1664262839.git.gmuthukrishn@marvell.com \
--to=gmuthukrishn@marvell.com \
--cc=anoobj@marvell.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@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).