From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id C35D4A0679 for ; Mon, 1 Apr 2019 16:39:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 92734343C; Mon, 1 Apr 2019 16:39:36 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id BFA1311A4 for ; Mon, 1 Apr 2019 16:39:34 +0200 (CEST) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Apr 2019 07:39:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,297,1549958400"; d="scan'208";a="136590879" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.35]) by fmsmga008.fm.intel.com with SMTP; 01 Apr 2019 07:39:31 -0700 Received: by (sSMTP sendmail emulation); Mon, 01 Apr 2019 15:39:28 +0100 Date: Mon, 1 Apr 2019 15:39:28 +0100 From: Bruce Richardson To: Ferruh Yigit Cc: Thomas Monjalon , Wenzhuo Lu , Qi Zhang , dev@dpdk.org, cathal.ohare@intel.com, john.mcnamara@intel.com Message-ID: <20190401143928.GA1441@bricha3-MOBL.ger.corp.intel.com> References: <1551340136-83843-1-git-send-email-wenzhuo.lu@intel.com> <1553581011-94181-1-git-send-email-wenzhuo.lu@intel.com> <079356fb-7de6-b091-3266-56e04b05b2e8@intel.com> <2061322.Qldrv329ue@xps> <1af99378-b51a-fe64-6bba-7b8dd5f67e07@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline In-Reply-To: <1af99378-b51a-fe64-6bba-7b8dd5f67e07@intel.com> User-Agent: Mutt/1.11.4 (2019-03-13) Subject: Re: [dpdk-dev] [PATCH v7 0/8] Support vector instructions on ICE 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" Message-ID: <20190401143928.nnMZLXdXLFAfjpxQ_LyDwmk9owvtvnV-zPxt_WfwxFY@z> On Mon, Apr 01, 2019 at 01:51:38PM +0100, Ferruh Yigit wrote: > On 3/31/2019 4:52 PM, Thomas Monjalon wrote: > > 26/03/2019 10:50, Ferruh Yigit: > >>> Wenzhuo Lu (8): > >>> net/ice: fix Tx function setting > >>> net/ice: add pointer for queue buffer release > >>> net/ice: support vector SSE in RX > >>> net/ice: support Rx scatter SSE vector > >>> net/ice: support Tx SSE vector > >>> net/ice: support Rx AVX2 vector > >>> net/ice: support Rx scatter AVX2 vector > >>> net/ice: support vector AVX2 in TX > >> > >> This version (v7) pulled from next-net-intel to next-net. > > > > I assume these patches have been tested, or at least compiled. > > However, when running devtools/test-meson-builds.sh, there is a > > compilation error for build-x86-default: > > > > In file included from ../drivers/net/ice/ice_ethdev.h:10: > > rte_ethdev_pci.h:38:10: fatal error: 'rte_pci.h' file not found > > I tested this with meson but not able to catch the issue. Perhaps for my case > dependencies were build fast enough to cause a problem. > That should be a problem with the meson builds. While with make builds, the headers files are picked up after they are copied to the "include" directory by the build process, in meson no such copying occurs and the header files are picked up by having the paths to them passed in the "dependency object" to each build. If the dependency does not exist then the build will never pass, irrespective of ordering, and if the dependency exists, the build will always find the header in its original location. [The biggest benefit of this is that when building with ninja there are no dependencies between the individual .c files - each one can be compiled in parallel with all the others. It's only at the linking step that we need to wait for previous jobs to complete] In terms of this specific error with the header - did it get root caused? Since it occurs on the "default" path, I'd suggest the fallback handling in the meson.build file for the absense of AVX may be faulty, e.g. are you replacing c flags or dependencies rather than appending to them? /Bruce