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 EB4C4A04B1; Fri, 28 Aug 2020 12:20:09 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C5B8E1C10A; Fri, 28 Aug 2020 12:20:09 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id B29771B951 for ; Fri, 28 Aug 2020 12:20:08 +0200 (CEST) IronPort-SDR: 6MleUCXZy0kjr4LdbtW6lazKDdPgZAr/5XDMHhxH6Gc2O2llAChQ8BJ8FkKRyuPbx8RK2XuNoW d9aR5UJUJ/mA== X-IronPort-AV: E=McAfee;i="6000,8403,9726"; a="136186984" X-IronPort-AV: E=Sophos;i="5.76,363,1592895600"; d="scan'208";a="136186984" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Aug 2020 03:20:06 -0700 IronPort-SDR: bs7Db/gH5Ecrv8/prMUVrDQxKTs8LAYFT2SYLMixPGwiJ1FcJNm+uFBleAMLtXSzTNd//1vKwL pv/GvgGK/xag== X-IronPort-AV: E=Sophos;i="5.76,363,1592895600"; d="scan'208";a="475624803" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.22.193]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 28 Aug 2020 03:20:05 -0700 Date: Fri, 28 Aug 2020 11:20:02 +0100 From: Bruce Richardson To: Juraj =?utf-8?Q?Linke=C5=A1?= Cc: "dev@dpdk.org" Message-ID: <20200828102002.GB575@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Subject: Re: [dpdk-dev] DPDK 20.08 meson build testpmd not detecting all NUMA nodes 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 Fri, Aug 28, 2020 at 09:26:12AM +0000, Juraj Linkeš wrote: > Hello DPDK devs, > > I've meson built (using just meson build && ninja -C build) dpdk-20.08 (downloaded from the site) on a Taishan arm server and dpdk-testpmd is incorrectly detecting NUMA nodes on the system: > EAL: Detected 16 lcore(s) > EAL: Detected 1 NUMA nodes > > lscpu report 4 NUMA nodes: > NUMA node0 CPU(s): 0-15 > NUMA node1 CPU(s): 16-31 > NUMA node2 CPU(s): 32-47 > NUMA node3 CPU(s): 48-63 > > When built with make T=arm64-armv8a-linuxapp-gcc testpmd is detecting NUMA nodes correctly: > EAL: Detected 64 lcore(s) > EAL: Detected 4 NUMA nodes > > Any idea what's the difference between the builds? I've looked at NUMA config options but those seem ok to me: > grep NUMA arm64-armv8a-linuxapp-gcc/.config build/rte_build_config.h > arm64-armv8a-linuxapp-gcc/.config:CONFIG_RTE_MAX_NUMA_NODES=8 > arm64-armv8a-linuxapp-gcc/.config:# a "type" is a combination of page size and NUMA node. total number of memseg > arm64-armv8a-linuxapp-gcc/.config:CONFIG_RTE_EAL_NUMA_AWARE_HUGEPAGES=y > arm64-armv8a-linuxapp-gcc/.config:CONFIG_RTE_LIBRTE_VHOST_NUMA=y > build/rte_build_config.h:#define RTE_EAL_NUMA_AWARE_HUGEPAGES 1 > build/rte_build_config.h:#define RTE_HAS_LIBNUMA 1 > build/rte_build_config.h:#define RTE_LIBRTE_VHOST_NUMA 1 > build/rte_build_config.h:#define RTE_MAX_NUMA_NODES 4 > > Any pointers are welcome. > What is the max lcores value in your build config? Do you know what settings are being chosen for your platform in config/arm/meson.build? Regards, /Bruce