DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Brian Dooley <brian.dooley@intel.com>, Kai Ji <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
	Ciara Power <ciara.power@intel.com>
Subject: RE: [EXT] [PATCH v7] crypto/qat: default to IPsec MB for computations
Date: Tue, 20 Jun 2023 12:43:10 +0000	[thread overview]
Message-ID: <CO6PR18MB4484E731A29FFDE5F616528DD85CA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230620105617.339222-1-brian.dooley@intel.com>

> Pre and post computations currently use the OpenSSL library by default.
> This patch changes the default option to Intel IPsec MB library version
> 1.4 for the required computations. If this version of IPsec is not met
> it will fallback to use OpenSSL. ARM will always default to using
> OpenSSL as ARM IPsec MB does not support the necessary algorithms.
> 
> Added version checks for libipsecmb and libcrypto into meson build.
> Added directives for detecting IPsec MB or OpenSSL.
> 
> Signed-off-by: Brian Dooley <brian.dooley@intel.com>
> Acked-by: Kai Ji <kai.ji@intel.com>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> Acked-by: Ciara Power <ciara.power@intel.com>
> ---
> v7:
> Rebase for-main

Applied to dpdk-next-crypto

Thanks.

      reply	other threads:[~2023-06-20 12:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 15:23 [PATCH v1] crypto/qat: add IPsec MB AES and DES Docsis support Brian Dooley
2023-05-19 10:50 ` [PATCH v2] crypto/qat: default to IPsec MB for pre and post computes Brian Dooley
2023-05-22 14:39   ` [PATCH v3] " Brian Dooley
2023-05-23 14:10     ` Ji, Kai
2023-05-25  7:28     ` [EXT] " Akhil Goyal
2023-05-26 10:26     ` [PATCH v4] crypto/qat: default to IPsec MB for computations Brian Dooley
2023-06-02 11:24       ` De Lara Guarch, Pablo
2023-06-06 10:28       ` [PATCH v5] " Brian Dooley
2023-06-08 12:25         ` Power, Ciara
2023-06-14 18:23         ` [EXT] " Akhil Goyal
2023-06-16 16:02         ` [PATCH v6] " Brian Dooley
2023-06-20 10:56           ` [PATCH v7] " Brian Dooley
2023-06-20 12:43             ` 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=CO6PR18MB4484E731A29FFDE5F616528DD85CA@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=brian.dooley@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@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).