From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, roy.fan.zhang@intel.com,
Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v4 0/3] cryptodev: move dh type from xform to dh op
Date: Wed, 27 Apr 2022 08:43:57 +0100 [thread overview]
Message-ID: <20220427074400.2091-1-arkadiuszx.kusztal@intel.com> (raw)
Operation type (PUBLIC_KEY_GENERATION, SHARED_SECRET) should
be free to choose for any operation. One xform/session should
be enough to perform both DH operations, if op_type would be xform
member, session would have to be to be created twice for the same
group. Similar problem would be observed in sessionless case.
Additionally, it will help extend DH to support Elliptic Curves.
v4:
- changed op_type coment
- added openssl fix
Arek Kusztal (3):
cryptodev: move dh type from xform to dh op
crypto/openssl: move dh type from xform to dh op
test/crypto: move dh type from xform to dh op
app/test/test_cryptodev_asym.c | 11 +++---
drivers/crypto/openssl/rte_openssl_pmd.c | 54 ++--------------------------
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 26 --------------
lib/cryptodev/rte_crypto_asym.h | 14 ++++----
4 files changed, 16 insertions(+), 89 deletions(-)
--
2.13.6
next reply other threads:[~2022-04-27 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:43 Arek Kusztal [this message]
2022-04-27 7:43 ` [PATCH v4 1/3] " Arek Kusztal
2022-04-27 8:11 ` Zhang, Roy Fan
2022-05-10 9:26 ` Ji, Kai
2022-04-27 7:43 ` [PATCH v4 2/3] crypto/openssl: " Arek Kusztal
2022-04-27 8:11 ` Zhang, Roy Fan
2022-04-27 7:44 ` [PATCH v4 3/3] test/crypto: " Arek Kusztal
2022-04-27 8:12 ` Zhang, Roy Fan
2022-04-27 8:12 ` [PATCH v4 0/3] cryptodev: " Zhang, Roy Fan
2022-04-27 15:57 ` [EXT] " Akhil Goyal
2022-04-29 6:25 ` Kusztal, ArkadiuszX
2022-05-06 12:05 ` Kusztal, ArkadiuszX
2022-05-10 9:43 ` Ji, Kai
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=20220427074400.2091-1-arkadiuszx.kusztal@intel.com \
--to=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@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).