From: Kai Ji <kai.ji@intel.com>
To: dev@dpdk.org
Cc: Kai Ji <kai.ji@intel.com>
Subject: [dpdk-dev v2 1/2] build: add in option for qat use intel ipsec-mb lib
Date: Tue, 17 May 2022 22:16:51 +0800 [thread overview]
Message-ID: <20220517141652.53769-1-kai.ji@intel.com> (raw)
In-Reply-To: <20220407152931.8771-1-roy.fan.zhang@intel.com>
Add in build option for QAT pmd use intel ipsec-mb lib
instead openssl for precompute partial hash & aes.
Signed-off-by: Kai Ji <kai.ji@intel.com>
---
drivers/common/qat/meson.build | 12 ++++++++++++
meson_options.txt | 2 ++
2 files changed, 14 insertions(+)
diff --git a/drivers/common/qat/meson.build b/drivers/common/qat/meson.build
index b7027f3164..d6eaff3e0e 100644
--- a/drivers/common/qat/meson.build
+++ b/drivers/common/qat/meson.build
@@ -35,6 +35,18 @@ if qat_crypto and not libcrypto.found()
'missing dependency, libcrypto')
endif
+if get_option('qat_libipsecmb')
+ IMB_required_ver = '1.0.0'
+ libipsecmb = cc.find_library('IPSec_MB', required: false)
+ if not lib.found()
+ build = false
+ reason = 'missing dependency, "libIPSec_MB"'
+ else
+ ext_deps += libipsecmb
+ dpdk_conf.set('RTE_QAT_LIBIPSECMB', true)
+ endif
+endif
+
# The driver should not build if both compression and crypto are disabled
#FIXME common code depends on compression files so check only compress!
if not qat_compress # and not qat_crypto
diff --git a/meson_options.txt b/meson_options.txt
index 7c220ad68d..e48e7dd966 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -42,6 +42,8 @@ option('mbuf_refcnt_atomic', type: 'boolean', value: true, description:
'Atomically access the mbuf refcnt.')
option('platform', type: 'string', value: 'native', description:
'Platform to build, either "native", "generic" or a SoC. Please refer to the Linux build guide for more information.')
+option('qat_libipsecmb', type: 'boolean', value: false, description:
+ 'use ipsec mb lib instead openssl for QAT pmd')
option('enable_trace_fp', type: 'boolean', value: false, description:
'enable fast path trace points.')
option('tests', type: 'boolean', value: true, description:
--
2.17.1
next prev parent reply other threads:[~2022-05-17 14:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 15:29 [PATCH] crypto/qat: use intel-ipsec-mb for partial hash Fan Zhang
2022-04-14 18:45 ` [External] : " Changchun Zhang
2022-04-20 18:14 ` Changchun Zhang
2022-05-17 14:21 ` Ji, Kai
2022-05-17 14:16 ` Kai Ji [this message]
2022-05-17 14:16 ` [dpdk-dev v2 2/2] crypto/qat: use intel-ipsec-mb for partial hash & aes Kai Ji
2022-05-17 15:01 ` Zhang, Roy Fan
2022-05-17 15:00 ` [dpdk-dev v2 1/2] build: add in option for qat use intel ipsec-mb lib Zhang, Roy Fan
2022-05-18 8:04 ` Bruce Richardson
2022-05-18 10:26 ` Ferruh Yigit
2022-05-18 10:33 ` Bruce Richardson
2022-05-18 13:35 ` Ji, Kai
2022-05-19 9:14 ` Zhang, Roy Fan
2022-05-19 10:22 ` Bruce Richardson
2022-05-19 12:25 ` Zhang, Roy Fan
2022-05-19 14:39 ` Bruce Richardson
2022-05-19 9:22 ` Zhang, Roy Fan
2022-05-19 11:15 ` Ferruh Yigit
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=20220517141652.53769-1-kai.ji@intel.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
/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).