DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: "Power, Ciara" <ciara.power@intel.com>,
	"Ji, Kai" <kai.ji@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ji, Kai" <kai.ji@intel.com>, "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Subject: RE: [dpdk-dev v7] crypto/qat: use intel-ipsec-mb for partial hash & aes
Date: Tue, 21 Jun 2022 17:45:21 +0000	[thread overview]
Message-ID: <CO6PR18MB4484A21C2A614866FE87F902D8B39@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB3821191950824B29B4D3D681E6AF9@MN2PR11MB3821.namprd11.prod.outlook.com>

> Hi Kai,
> 
> > Since openssl 3.0 now deprecates the low level API QAT required to perform
> > partial hash & aes operation when creating the session. This patch add in
> > qat_ipsec_mb_lib driver parameter to allow QAT PMD to switch APIs
> > between openssl and intel ipsec-mb library.
> >
> > Signed-off-by: Kai Ji <kai.ji@intel.com>
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> Acked-by: Ciara Power <ciara.power@intel.com>

Applied to dpdk-next-crypto

      reply	other threads:[~2022-06-21 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <http://patches.dpdk.org/project/dpdk/patch/20220525165218.10926-1-kai.ji@intel.com/>
2022-05-26 10:47 ` [dpdk-dev v4] " Kai Ji
2022-05-26 13:43   ` [EXT] " Akhil Goyal
2022-05-26 13:43     ` Akhil Goyal
2022-05-27  8:55   ` [dpdk-dev v5] " Kai Ji
2022-05-27 12:26     ` Zhang, Roy Fan
2022-05-30 10:21     ` [dpdk-dev v6] " Kai Ji
2022-06-13 17:02       ` [dpdk-dev v7] " Kai Ji
2022-06-17 11:26         ` Power, Ciara
2022-06-21 17:45           ` 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=CO6PR18MB4484A21C2A614866FE87F902D8B39@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.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).