From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id C56102BAA for ; Sun, 26 Aug 2018 16:52:27 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Aug 2018 07:52:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.53,291,1531810800"; d="scan'208";a="69243738" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga006.jf.intel.com with ESMTP; 26 Aug 2018 07:52:25 -0700 Received: from fmsmsx115.amr.corp.intel.com (10.18.116.19) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 26 Aug 2018 07:52:25 -0700 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.210]) by fmsmsx115.amr.corp.intel.com ([169.254.4.182]) with mapi id 14.03.0319.002; Sun, 26 Aug 2018 07:52:24 -0700 From: "Wiles, Keith" To: waqas ahmed CC: "users@dpdk.org" Thread-Topic: [dpdk-users] Invalid NUMA socket Thread-Index: AQHUPQK3W6XMcBtZKUicJyekOnPPi6TSlB0A Date: Sun, 26 Aug 2018 14:52:23 +0000 Message-ID: <6E42D8F7-5E0D-4943-88F8-01A3F33AD0E6@intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.103.169] Content-Type: text/plain; charset="us-ascii" Content-ID: <94F744C4F5552044A19E6E7EE09ADED3@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] Invalid NUMA socket X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Aug 2018 14:52:28 -0000 > On Aug 26, 2018, at 1:04 AM, waqas ahmed wrote= : >=20 > Hi everyone, > we have dual socket xeon cpu, and we have intel 52899 10g nic having pci > address 0000:05:00.0. while running helloworld app EAL log tells that th= is > device is found on numa socket -1 ! it should be found on either numa nod= e > 0 or 1? > ------------------------------------------------------------------------ > numactl --hardware gives following output > available: 2 nodes (0-1) > node 0 cpus: 0 1 2 3 > node 0 size: 16036 MB > node 0 free: 10268 MB > node 1 cpus: 4 5 6 7 > node 1 size: 16125 MB > node 1 free: 11977 MB > node distances: > node 0 1 > 0: 10 21 > 1: 21 10 Can you tell us the version of DPDK and the OS/version. I assume you are not running inside a VM, right? >=20 > DPDK helloworld app log > -------------------------------------------------------------------------= -- > EAL: Detected 8 lcore(s) > EAL: Multi-process socket /var/run/.rte_unix > EAL: Probing VFIO support... > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10c9 net_e1000_igb > EAL: PCI device 0000:01:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10c9 net_e1000_igb > EAL: PCI device 0000:05:00.0 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > EAL: PCI device 0000:05:00.1 on NUMA socket -1 > EAL: Invalid NUMA socket, default to 0 > EAL: probe driver: 8086:10fb net_ixgbe > hello from core 2 > hello from core 3 > hello from core 4 > hello from core 5 > hello from core 6 > hello from core 7 > hello from core 1 You can also change the hello world app and call rte_socket_id() and print = that value out too? Regards, Keith