From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>,
"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Ji, Kai" <kai.ji@intel.com>
Subject: RE: [RFC] cryptodev: refactor sm2, add plain message flag
Date: Fri, 19 Jan 2024 09:18:50 +0000 [thread overview]
Message-ID: <CO6PR18MB4484D6FC98AE3B2193059910D8702@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <SN7PR11MB7639713C56FC99CCDAF024A4E6CBA@SN7PR11MB7639.namprd11.prod.outlook.com>
Hi Ciara/Arek,
> Hi Akhil,
>
> > -----Original Message-----
> > From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> > Sent: Friday, August 11, 2023 6:40 PM
> > To: dev@dpdk.org
> > Cc: gakhil@marvell.com; Ji, Kai <kai.ji@intel.com>; Power, Ciara
> > <ciara.power@intel.com>; Kusztal, ArkadiuszX
> <arkadiuszx.kusztal@intel.com>
> > Subject: [RFC] cryptodev: refactor sm2, add plain message flag
> >
> > SM2 asymmetric crypto operation was split into cipher and signature
> operation.
> > Now it corresponds to the other crypto algorithms and facilitates addition of
> other
> > SM2 components like the SM2 key exchange.
> >
> > Flag to distinguish between a plain message or a hash used for signature was
> > added to the DSA, ECDSA and SM2.
> >
> > Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> > ---
> > lib/cryptodev/rte_crypto_asym.h | 116 +++++++++++++++++---------------
> > 1 file changed, 63 insertions(+), 53 deletions(-)
>
> Due to ongoing discussion and rework needed on this patch, it will be picked
> back up for release, as we did not make 23.11 RC1.
>
Is it planned for 24.03? Any update?
prev parent reply other threads:[~2024-01-19 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 17:39 Arkadiusz Kusztal
2023-08-14 7:49 ` [EXT] " Gowrishankar Muthukrishnan
2023-09-17 15:59 ` Kusztal, ArkadiuszX
2023-09-21 4:26 ` Gowrishankar Muthukrishnan
2023-10-04 9:34 ` Power, Ciara
2024-01-19 9:18 ` Akhil Goyal [this message]
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=CO6PR18MB4484D6FC98AE3B2193059910D8702@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--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).