From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 8FCF02BA4 for ; Sun, 26 Aug 2018 19:48:06 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Aug 2018 10:48:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.53,291,1531810800"; d="scan'208";a="252060517" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga005.jf.intel.com with ESMTP; 26 Aug 2018 10:48:05 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 26 Aug 2018 10:48:04 -0700 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.210]) by fmsmsx156.amr.corp.intel.com ([169.254.13.131]) with mapi id 14.03.0319.002; Sun, 26 Aug 2018 10:48:05 -0700 From: "Wiles, Keith" To: waqas ahmed CC: "users@dpdk.org" Thread-Topic: [dpdk-users] Invalid NUMA socket Thread-Index: AQHUPQK3W6XMcBtZKUicJyekOnPPi6TSlB0AgAAudYCAAAKfAA== Date: Sun, 26 Aug 2018 17:48:04 +0000 Message-ID: References: <6E42D8F7-5E0D-4943-88F8-01A3F33AD0E6@intel.com> 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: <8161E1B6430E9B4A9A91C97B66BD5816@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 17:48:07 -0000 > On Aug 26, 2018, at 12:38 PM, waqas ahmed wrot= e: >=20 > many thanks keith for help > here are the details > dpdk-18.02.2 > $> lsb_release -a > Distributor ID: Ubuntu > Description: Ubuntu 17.04 > Release: 17.04 > Codename: zesty > $> uname -r > 4.10.0-19-generic > ---------------------------------------- > following is the output by calling rte_socket_id(), which associate lcore= s to their numa socket correctly, i am just got curious about why nic is no= t associated with its numa socket! > i am working on remote server. Well I assume it should be working too, but I would start by looking at the= code that prints out the -1 value. > ---------------------------------------- > 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 1 on socket 0 > hello from core 2 on socket 0 > hello from core 3 on socket 0 > hello from core 4 on socket 1 > hello from core 5 on socket 1 > hello from core 6 on socket 1 > hello from core 7 on socket 1 > hello from core 0 on socket 0 > ------------------------------------------------- > Regards > Ahmed =20 >=20 >=20 > On Sun, Aug 26, 2018 at 7:52 PM Wiles, Keith wrot= e: >=20 >=20 > > On Aug 26, 2018, at 1:04 AM, waqas ahmed wro= te: > >=20 > > Hi everyone, > > we have dual socket xeon cpu, and we have intel 52899 10g nic having pc= i > > address 0000:05:00.0. while running helloworld app EAL log tells that = this > > device is found on numa socket -1 ! it should be found on either numa n= ode > > 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 >=20 > Can you tell us the version of DPDK and the OS/version. >=20 > I assume you are not running inside a VM, right? >=20 > >=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 >=20 > You can also change the hello world app and call rte_socket_id() and prin= t that value out too? >=20 > Regards, > Keith >=20 Regards, Keith