From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2D22BA0503; Wed, 18 May 2022 12:33:19 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C4CE340156; Wed, 18 May 2022 12:33:18 +0200 (CEST) Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id AF5EA400D6 for ; Wed, 18 May 2022 12:33:16 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1652869997; x=1684405997; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=QBKM9IRsUn3TRuYWw0OvXWOF9pJf1NwZ7tLv/XPEHVk=; b=jSrAfXyVGBHsJKDr1X6PlHPZc6FU7kmqpgEm5vzFTgEErVzdfLUJTrEn aLkx1/t05pTFLUVnGvR03nuoXcwC6YTOPys+V6INFVCKBbppwNqYvTCS4 QSvmEjkofiNJ087x3xaYvcGPsilsJ+BUdUYDIQ06nzulDn0G/WMILrLFT Lc7GsLt14U0Z6aVjuGzW/lE2bdUFhnBRIG53MtRsoc/7Mf0dNDlIVQ9fW GyhpeJMWbuR9djsMMSCVc+vmgDWZhSM53FjUfpqtmfcdN1pTbg6fJaKQW RQeVo1e9+gnVn3f54hQkmivOzAGhhcvfFO7Q0pxxDAsRtPI43dh2lI29g w==; X-IronPort-AV: E=McAfee;i="6400,9594,10350"; a="332221461" X-IronPort-AV: E=Sophos;i="5.91,234,1647327600"; d="scan'208";a="332221461" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 May 2022 03:33:15 -0700 X-IronPort-AV: E=Sophos;i="5.91,234,1647327600"; d="scan'208";a="673356410" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.3.104]) by fmsmga002-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 18 May 2022 03:33:13 -0700 Date: Wed, 18 May 2022 11:33:10 +0100 From: Bruce Richardson To: Ferruh Yigit Cc: Kai Ji , dev@dpdk.org, roy.fan.zhang@intel.com Subject: Re: [dpdk-dev v2 1/2] build: add in option for qat use intel ipsec-mb lib Message-ID: References: <20220407152931.8771-1-roy.fan.zhang@intel.com> <20220517141652.53769-1-kai.ji@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Wed, May 18, 2022 at 11:26:27AM +0100, Ferruh Yigit wrote: > On 5/18/2022 9:04 AM, Bruce Richardson wrote: > > On Tue, May 17, 2022 at 10:16:51PM +0800, Kai Ji wrote: > > > Add in build option for QAT pmd use intel ipsec-mb lib > > > instead openssl for precompute partial hash & aes. > > > > > > Signed-off-by: Kai Ji > > > --- > > > 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 > > > + > > > > In general it's not a good idea for individual drivers to add top-level > > meson.build options. If every driver does this for all its options we will > > have an unmanageable set of hundreds of options. Unfortunately, though, I > > don't see a really good way to replace this with something other than a > > build option - I assume it's not just good enough to check which of the > > dependencies is found/not-found? Is there some way that this can be a > > generic option, that may be applicable to other drivers? Could the option > > be instead to prioritize FIPs compatibility? > > > > +1 to not have top level meson option for a driver. > > Will it work to give priority to intel-ipsec-mb lib, like when ipsec-mb > library exists use it, else use openssl? Looking at the patch a bit more, is there a reason why this cannot be made a run-time option when both libraries are available?