From: Anoob Joseph <anoobj@marvell.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
Declan Doherty <declan.doherty@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Anoob Joseph <anoobj@marvell.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Arek Kusztal <arkadiuszx.kusztal@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
Narayana Prasad <pathreya@marvell.com>,
Shally Verma <shallyv@marvell.com>,
Ankur Dwivedi <adwivedi@marvell.com>,
Sunila Sahu <ssahu@marvell.com>, <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/4] add ECPM support
Date: Thu, 5 Dec 2019 21:07:56 +0530 [thread overview]
Message-ID: <1575560280-3261-1-git-send-email-anoobj@marvell.com> (raw)
This series adds support for ECPM (Elliptic Curve Point Multiplication)
asymmetric operations. Library changes and PMD changes for
crypto_octeontx & crypto_octeontx2 is added. The final patch adds
the required test vectors and verification routines.
Balakrishna Bhamidipati (1):
lib/crypto: add support for EC Point Multiplication
Sunila Sahu (3):
crypto/octeontx: add EC Point Mul support
crypto/octeontx2: add EC Point Mul support
app/test: add EC point multiplication test
app/test/test_cryptodev_asym.c | 177 +++++++++++
app/test/test_cryptodev_asym_util.h | 11 +
app/test/test_cryptodev_ecpm_test_vectors.h | 353 +++++++++++++++++++++
doc/guides/cryptodevs/features/default.ini | 1 +
doc/guides/cryptodevs/features/octeontx.ini | 1 +
doc/guides/cryptodevs/features/octeontx2.ini | 1 +
drivers/common/cpt/cpt_mcode_defines.h | 2 +
drivers/common/cpt/cpt_ucode_asym.h | 85 +++++
.../crypto/octeontx/otx_cryptodev_capabilities.c | 11 +
drivers/crypto/octeontx/otx_cryptodev_ops.c | 23 ++
.../crypto/octeontx2/otx2_cryptodev_capabilities.c | 11 +
drivers/crypto/octeontx2/otx2_cryptodev_ops.c | 22 ++
lib/librte_cryptodev/rte_crypto_asym.h | 17 +
lib/librte_cryptodev/rte_cryptodev.c | 1 +
14 files changed, 716 insertions(+)
create mode 100644 app/test/test_cryptodev_ecpm_test_vectors.h
--
2.7.4
next reply other threads:[~2019-12-05 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 15:37 Anoob Joseph [this message]
2019-12-05 15:37 ` [dpdk-dev] [PATCH 1/4] lib/crypto: add support for EC Point Multiplication Anoob Joseph
2020-01-13 12:43 ` Akhil Goyal
2020-01-14 6:44 ` Anoob Joseph
2019-12-05 15:37 ` [dpdk-dev] [PATCH 2/4] crypto/octeontx: add EC Point Mul support Anoob Joseph
2019-12-05 15:37 ` [dpdk-dev] [PATCH 3/4] crypto/octeontx2: " Anoob Joseph
2019-12-05 15:38 ` [dpdk-dev] [PATCH 4/4] app/test: add EC point multiplication test Anoob Joseph
2020-01-15 12:56 ` [dpdk-dev] [PATCH v2 0/4] add ECPM support Anoob Joseph
2020-01-15 12:56 ` [dpdk-dev] [PATCH v2 1/4] cryptodev: support ECPM Anoob Joseph
2020-01-15 15:49 ` Akhil Goyal
2020-01-15 12:56 ` [dpdk-dev] [PATCH v2 2/4] crypto/octeontx: add ECPM support Anoob Joseph
2020-01-15 12:56 ` [dpdk-dev] [PATCH v2 3/4] crypto/octeontx2: " Anoob Joseph
2020-01-15 12:56 ` [dpdk-dev] [PATCH v2 4/4] app/test: add ECPM tests Anoob Joseph
2020-01-15 15:49 ` [dpdk-dev] [PATCH v2 0/4] add ECPM support 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=1575560280-3261-1-git-send-email-anoobj@marvell.com \
--to=anoobj@marvell.com \
--cc=adwivedi@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=jerinj@marvell.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pathreya@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).