From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>
Cc: <anoobj@marvell.com>, Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: [PATCH v1 0/4] test/cryptodev: add ECDH tests
Date: Thu, 26 Oct 2023 13:45:08 +0530 [thread overview]
Message-ID: <cover.1698307299.git.gmuthukrishn@marvell.com> (raw)
This patch series adds ECDH testsuite. It also enables ECDH
support in CNXK PMD.
Gowrishankar Muthukrishnan (4):
test/cryptodev: add ECDH tests
crypto/cnxk: use generic EC opcodes
crypto/cnxk: change order of ECFPM params
crypto/cnxk: add ECDH support
app/test/test_cryptodev_asym.c | 729 ++++++++++++++++++
app/test/test_cryptodev_asym_util.h | 12 +
app/test/test_cryptodev_ecdh_test_vectors.h | 577 ++++++++++++++
app/test/test_cryptodev_ecdsa_test_vectors.h | 3 +
doc/guides/cryptodevs/features/cn10k.ini | 1 +
doc/guides/cryptodevs/features/cn9k.ini | 1 +
drivers/common/cnxk/roc_ae.h | 21 +-
drivers/crypto/cnxk/cn10k_cryptodev_ops.c | 12 +
drivers/crypto/cnxk/cnxk_ae.h | 240 ++++--
drivers/crypto/cnxk/cnxk_cryptodev.h | 2 +-
.../crypto/cnxk/cnxk_cryptodev_capabilities.c | 14 +
11 files changed, 1543 insertions(+), 69 deletions(-)
create mode 100644 app/test/test_cryptodev_ecdh_test_vectors.h
--
2.25.1
next reply other threads:[~2023-10-26 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 8:15 Gowrishankar Muthukrishnan [this message]
2023-10-26 8:15 ` [PATCH v1 1/4] " Gowrishankar Muthukrishnan
2023-10-30 18:48 ` Akhil Goyal
2023-11-08 13:17 ` [PATCH v2] " Gowrishankar Muthukrishnan
2023-11-09 20:24 ` Akhil Goyal
2023-10-26 8:15 ` [PATCH v1 2/4] crypto/cnxk: use generic EC opcodes Gowrishankar Muthukrishnan
2023-10-26 8:15 ` [PATCH v1 3/4] crypto/cnxk: change order of ECFPM params Gowrishankar Muthukrishnan
2023-10-26 8:15 ` [PATCH v1 4/4] crypto/cnxk: add ECDH support Gowrishankar Muthukrishnan
2023-10-30 18:49 ` 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=cover.1698307299.git.gmuthukrishn@marvell.com \
--to=gmuthukrishn@marvell.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@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).