From: "Power, Ciara" <ciara.power@intel.com>
To: "Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>,
Akhil Goyal <gakhil@marvell.com>,
Fan Zhang <fanzhang.oss@gmail.com>, "Ji, Kai" <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Poddar, Vikash ChandraX" <vikash.chandrax.poddar@intel.com>
Subject: RE: [PATCH v6] crypto/qat: support to enable insecure algorithms
Date: Thu, 8 Jun 2023 13:14:03 +0000 [thread overview]
Message-ID: <SN7PR11MB7639F7645B0C53753E0C9AEEE650A@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230529104529.2055773-1-vikash.chandrax.poddar@intel.com>
> -----Original Message-----
> From: Vikash Poddar <vikash.chandrax.poddar@intel.com>
> Sent: Monday 29 May 2023 11:45
> To: Akhil Goyal <gakhil@marvell.com>; Fan Zhang
> <fanzhang.oss@gmail.com>; Ji, Kai <kai.ji@intel.com>
> Cc: dev@dpdk.org; Poddar, Vikash ChandraX
> <vikash.chandrax.poddar@intel.com>
> Subject: [PATCH v6] crypto/qat: support to enable insecure algorithms
>
> All the insecure algorithms are default disable from cryptodev Gen 1,2,3 and
> 4.
> use qat_legacy_capa to enable all the legacy algorithms.
> These change effects both sym and asym insecure crypto algorithms.
>
> Signed-off-by: Vikash Poddar <vikash.chandrax.poddar@intel.com>
> ---
> Depends-on: patch-28182 ("[v2] common/qat: fix qat_dev_cmd_param
> corruption")
> v6:
> Rebased patch
> v5:
> Resolving apply patch warning
> v4:
> Resolved rebase conflict.
> v3:
> Rebased the patch.
> v2:
> Extend the support to enable the insecure algorithm in QAT Gen 1,3 and 4 for
> sym as well as asym.
Acked-by: Ciara Power <ciara.power@intel.com>
next prev parent reply other threads:[~2023-06-08 13:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 9:58 [PATCH] " Vikash Poddar
2023-05-23 9:14 ` [PATCH v2] " Vikash Poddar
2023-05-23 14:35 ` Ji, Kai
2023-05-25 7:56 ` [EXT] " Akhil Goyal
2023-05-25 16:10 ` [PATCH v3] " Vikash Poddar
2023-05-26 6:48 ` [PATCH v4] " Vikash Poddar
2023-05-29 6:32 ` [PATCH v5] " Vikash Poddar
2023-05-29 10:45 ` [PATCH v6] " Vikash Poddar
2023-06-08 13:14 ` Power, Ciara [this message]
2023-06-14 18:30 ` [EXT] " Akhil Goyal
2023-06-16 14:00 ` [PATCH v7 1/3] common/qat: fix qat_dev_cmd_param corruption Vikash Poddar
2023-06-16 14:00 ` [PATCH v7 2/3] crypto/qat: support to enable insecure algorithms Vikash Poddar
2023-06-16 14:00 ` [PATCH v7 3/3] test/crypto: skip asym test for " Vikash Poddar
2023-06-20 7:33 ` [EXT] [PATCH v7 1/3] common/qat: fix qat_dev_cmd_param corruption 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=SN7PR11MB7639F7645B0C53753E0C9AEEE650A@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=vikash.chandrax.poddar@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).