From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com [209.85.218.45]) by dpdk.org (Postfix) with ESMTP id F33CE2BAA for ; Sun, 26 Aug 2018 19:38:52 +0200 (CEST) Received: by mail-oi0-f45.google.com with SMTP id y207-v6so23419509oie.13 for ; Sun, 26 Aug 2018 10:38:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=iFKu+vnejDeZsKgw5ShEwEFmnUO96UBjn90IRppIAE4=; b=D1/TfVqURSjoZHcKRDJVjZNJIrnSS7Iuw0ILA2dnt1XsacuLPExuYV18BQzSfLZAXU CFpkJoI7VBGOpDtJoGwMv/JbRLh7k3XBjRU/+HC9GjdH1gO5M6KRtrgY/VzKdiSsQosM 3x7oz12UNf/GvBPjc2/she5FK26qHzHMtisK4/CtKrQVCvELLV6P5C9azYE1+tkIK5cp 1py5Lyt2P7dIpvqwdePpkJnpUdoKwhPpgsZKnwDJf/tMrZJQTkcalglNGWAf6oJZRB4x w+BDQhCtqnsAIwyZN3vvPsRoECkHWHKzqTi6homBQugrcF6expAi0IU1jkRZzFo4YUCN 5L2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=iFKu+vnejDeZsKgw5ShEwEFmnUO96UBjn90IRppIAE4=; b=dRGVKQV/y7/tx5JraDM7O86PwQrtS/ugS8zYxqaHbnPU6Lm4r0FnFvuf52ZmF9zBA2 oA7kbps7MuZgwUQMgFckLbXgkaSCaR12YZ2TVWbYd9+QNR4LL4jvNIfBJnPy2nN1AGgm 6O9jGfAqFm9GBdPAM4uty1VQN9CkQi12W/1HHd6TaVxLau5mYr1ClrkaikDgaeU3w2xt /UJaTCeYsFYxoLWxJT9iItZf+BorUrtcD+EQF4CrKPriyxDZCC/wnaxGvvVT/rcnTkVa swubemRmQ0Lhp23TGotiB04MxEz0SufRv1RJVK8udmOoweZZ+sBEBVyTxiTIYLv9JJB4 QdlA== X-Gm-Message-State: APzg51CsABchcLNywgH2IqDHMfaI3HfrNPDrWeg6WGcj1Qr9MgBHdbbv y5p+XKegW17anpkncQXYEPR/Z2IGdW5bXnY4axg= X-Google-Smtp-Source: ANB0VdaBWqzq7UeoEfJxyV9zhCCilwJA/8Ww4bKRADhFQ+7pnfY0Sw3dBCtXhkld6H8aVj+XxerftM/ff3uXo+pzKQA= X-Received: by 2002:aca:5dc5:: with SMTP id r188-v6mr10044955oib.320.1535305132206; Sun, 26 Aug 2018 10:38:52 -0700 (PDT) MIME-Version: 1.0 References: <6E42D8F7-5E0D-4943-88F8-01A3F33AD0E6@intel.com> In-Reply-To: <6E42D8F7-5E0D-4943-88F8-01A3F33AD0E6@intel.com> From: waqas ahmed Date: Sun, 26 Aug 2018 22:38:39 +0500 Message-ID: To: keith.wiles@intel.com, users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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:38:53 -0000 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 lcores to their numa socket correctly, i am just got curious about why nic is not associated with its numa socket! i am working on remote server. ---------------------------------------- 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 On Sun, Aug 26, 2018 at 7:52 PM Wiles, Keith wrote: > > > > On Aug 26, 2018, at 1:04 AM, waqas ahmed > wrote: > > > > 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 > this > > device is found on numa socket -1 ! it should be found on either numa > node > > 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? > > > > > 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 > >