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: [v1, 0/3] SM2 crypto algorithm support
Date: Fri, 28 Apr 2023 14:58:18 +0530 [thread overview]
Message-ID: <cover.1682652719.git.gmuthukrishn@marvell.com> (raw)
This patch series adds SM2 crypto algorithm support, along with tests
verified using Openssl.
Gowrishankar Muthukrishnan (3):
cryptodev: add SM2 asymmetric crypto algorithm
test/test_cryptodev_asym: add SM2 tests
crypto/openssl: add SM2 asymmetric crypto support
app/test/test_cryptodev_asym.c | 506 +++++++++++++++++++
app/test/test_cryptodev_sm2_test_vectors.h | 120 +++++
doc/guides/cryptodevs/features/default.ini | 1 +
doc/guides/cryptodevs/features/openssl.ini | 1 +
doc/guides/cryptodevs/openssl.rst | 1 +
doc/guides/rel_notes/release_23_07.rst | 7 +
drivers/crypto/openssl/openssl_pmd_private.h | 7 +
drivers/crypto/openssl/rte_openssl_pmd.c | 245 +++++++++
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 101 ++++
lib/cryptodev/rte_crypto_asym.h | 76 +++
lib/cryptodev/rte_cryptodev.c | 1 +
11 files changed, 1066 insertions(+)
create mode 100644 app/test/test_cryptodev_sm2_test_vectors.h
--
2.25.1
next reply other threads:[~2023-04-28 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 9:28 Gowrishankar Muthukrishnan [this message]
2023-04-28 9:28 ` [v1, 1/3] cryptodev: add SM2 asymmetric crypto algorithm Gowrishankar Muthukrishnan
2023-05-16 11:49 ` Akhil Goyal
2023-04-28 9:28 ` [v1, 2/3] test/test_cryptodev_asym: add SM2 tests Gowrishankar Muthukrishnan
2023-05-16 12:10 ` Akhil Goyal
2023-05-26 7:31 ` Gowrishankar Muthukrishnan
2023-05-26 8:42 ` Akhil Goyal
2023-04-28 9:28 ` [v1, 3/3] crypto/openssl: add SM2 asymmetric crypto support Gowrishankar Muthukrishnan
2023-04-28 15:17 ` Gowrishankar Muthukrishnan
2023-05-16 12:14 ` 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.1682652719.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).