From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3F9FDA04DD; Thu, 22 Oct 2020 15:52:51 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 48BCBA9DF; Thu, 22 Oct 2020 15:52:49 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 2CEA9A9CF for ; Thu, 22 Oct 2020 15:52:46 +0200 (CEST) IronPort-SDR: 8Fe2RCkQJ7owZoTy3IfKJinV5FrRsfSrEFu+bwykkYZwFmzSiAJoXq+KlpLddAr2U4Yth9RCJS Oj+Muu8gDg9Q== X-IronPort-AV: E=McAfee;i="6000,8403,9781"; a="231722034" X-IronPort-AV: E=Sophos;i="5.77,404,1596524400"; d="scan'208";a="231722034" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Oct 2020 06:52:44 -0700 IronPort-SDR: PfvE+3+OyBm2XzeJaquhLDQouTj8HWQBYFuXr8tSo3lRK1U7kmVdMe+1UCJ87pnfhU1p7/0okI +p2YU1QxjQ0Q== X-IronPort-AV: E=Sophos;i="5.77,404,1596524400"; d="scan'208";a="321385573" Received: from bricha3-mobl.ger.corp.intel.com ([10.214.249.80]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 22 Oct 2020 06:52:43 -0700 Date: Thu, 22 Oct 2020 14:52:38 +0100 From: Bruce Richardson To: Sarosh Arif Cc: dev Message-ID: <20201022135238.GA90@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] setting parameters in meson build system X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Oct 22, 2020 at 04:43:50PM +0500, Sarosh Arif wrote: > Hello, > > I was using make build system previously, but since it is removed from > dpdk now, I am trying to figure out how to enable/disable certain > things using meson, > > Previously we were able to set some parameters using .config file. > Some examples of these parameters are: > > CONFIG_RTE_LIBRTE_I40E_PMD=y > CONFIG_RTE_LIBRTE_I40E_DEBUG_RX=n > CONFIG_RTE_LIBRTE_I40E_DEBUG_TX=n > CONFIG_RTE_LIBRTE_I40E_DEBUG_TX_FREE=n > CONFIG_RTE_LIBRTE_I40E_RX_ALLOW_BULK_ALLOC=y > CONFIG_RTE_LIBRTE_I40E_INC_VECTOR=y > CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC=n > CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_PF=64 > CONFIG_RTE_LIBRTE_I40E_QUEUE_NUM_PER_VM=4 > > Can someone help me figure out how to enable/disable/change these > using the meson build system? > Enabling/disabling of specific drivers can be done using the "disable_drivers" meson option to disable drivers, otherwise the drivers will be enabled automatically if their pre-requisites are met. [In the case of i40e it has no pre-requisites beyond basic DPDK requirements so it's always enabled by default]. For the debug settings, there has been discussion onlist about having a global debug setting which can be scope limited in the same way as the log level APIs, but in the absense of support for that you can turn on the DEBUG settings by passing them as cflags (or c_args meson option) to the build. For the other settings, these are present in config/rte_config.h header file and can be edited directly there. However, we'd prefer if this wasn't necessary, so if you feel the defaults are not suitable for your use, please let the maintainers know, to see if we can adjust the default to be suitable for as many users as possible. Regards, /Bruce