DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Kai Ji <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>,
	Fan Zhang <fanzhang.oss@gmail.com>
Subject: RE: [EXTERNAL] [dpdk-dev v9 1/3] cryptodev: add ec points to sm2 op
Date: Tue, 30 Sep 2025 14:47:01 +0000	[thread overview]
Message-ID: <CO6PR18MB4484FF394ED5DFE3FBBF2570D81AA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250822111309.2506329-1-kai.ji@intel.com>

> In the case when PMD cannot support the full process of the SM2,
> but elliptic curve computation only, additional fields
> are needed to handle such a case.
> 
> Points C1, kP therefore were added to the SM2 crypto operation struct.
> 
> Signed-off-by: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> ---
Series applied to dpdk-next-crypto with some tweaks to release notes.

Thanks for the patience.



  parent reply	other threads:[~2025-09-30 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  9:36 [PATCH v8 0/3] " Arkadiusz Kusztal
2024-11-04  9:36 ` [PATCH v8 1/3] cryptodev: " Arkadiusz Kusztal
2024-11-06 10:08   ` [EXTERNAL] " Akhil Goyal
2024-11-06 15:17     ` Kusztal, ArkadiuszX
2025-08-22 11:13   ` [dpdk-dev v9 " Kai Ji
2025-08-22 11:13     ` [dpdk-dev v9 2/3] crypto/qat: add sm2 encryption/decryption function Kai Ji
2025-08-22 11:13     ` [dpdk-dev v9 3/3] app/test: add test sm2 C1/Kp test cases Kai Ji
2025-09-30 14:47     ` Akhil Goyal [this message]
2024-11-04  9:36 ` [PATCH v8 2/3] crypto/qat: add sm2 encryption/decryption function Arkadiusz Kusztal
2024-11-06 10:12   ` [EXTERNAL] " Akhil Goyal
2024-11-04  9:36 ` [PATCH v8 3/3] app/test: add test sm2 C1/Kp test cases Arkadiusz Kusztal

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=CO6PR18MB4484FF394ED5DFE3FBBF2570D81AA@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.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).