From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
To: <dev@dpdk.org>
Cc: <anoobj@marvell.com>, Akhil Goyal <gakhil@marvell.com>,
Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
Fan Zhang <fanzhang.oss@gmail.com>, Kai Ji <kai.ji@intel.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: [PATCH v3 0/3] SM2 crypto algorithm support
Date: Sun, 4 Jun 2023 15:12:43 +0530 [thread overview]
Message-ID: <cover.1685870993.git.gmuthukrishn@marvell.com> (raw)
This patch series adds SM2 crypto algorithm support, along with tests
verified using Openssl.
v3:
- sm2 xform contains hash param and key pair info moved into op.
Gowrishankar Muthukrishnan (3):
cryptodev: add SM2 asymmetric crypto algorithm
test/crypto: add asymmetric SM2 test cases
crypto/openssl: add SM2 asymmetric crypto support
app/test/test_cryptodev_asym.c | 581 +++++++++++++++++++
app/test/test_cryptodev_sm2_test_vectors.h | 129 ++++
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 | 9 +
drivers/crypto/openssl/openssl_pmd_private.h | 6 +
drivers/crypto/openssl/rte_openssl_pmd.c | 297 ++++++++++
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 48 ++
lib/cryptodev/rte_crypto_asym.h | 87 +++
lib/cryptodev/rte_cryptodev.c | 1 +
11 files changed, 1161 insertions(+)
create mode 100644 app/test/test_cryptodev_sm2_test_vectors.h
--
2.25.1
next reply other threads:[~2023-06-04 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 9:42 Gowrishankar Muthukrishnan [this message]
2023-06-04 9:42 ` [PATCH v3 1/3] cryptodev: add SM2 asymmetric crypto algorithm Gowrishankar Muthukrishnan
2023-06-06 20:01 ` Kusztal, ArkadiuszX
2023-06-07 3:39 ` Gowrishankar Muthukrishnan
2023-06-04 9:42 ` [PATCH v3 2/3] test/crypto: add asymmetric SM2 test cases Gowrishankar Muthukrishnan
2023-06-04 9:42 ` [PATCH v3 3/3] crypto/openssl: add SM2 asymmetric crypto support Gowrishankar Muthukrishnan
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.1685870993.git.gmuthukrishn@marvell.com \
--to=gmuthukrishn@marvell.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=kai.ji@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).