From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f173.google.com (mail-pl1-f173.google.com [209.85.214.173]) by dpdk.org (Postfix) with ESMTP id DD95E2E81 for ; Sun, 26 Aug 2018 22:48:27 +0200 (CEST) Received: by mail-pl1-f173.google.com with SMTP id d12-v6so181405pls.4 for ; Sun, 26 Aug 2018 13:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=aItUdumH08JU6N8OYOV8D532i+X0/mImH0WhN/CrnmQ=; b=cykRkHAf4PWLFxEcR4alFSuQ76nZpqPNMf+zEcgl2Og6dEh1Sk5y60rMX1IGuvFtSi vO8IOK4+0NaaWKNQ/DXkOZ8EkzkcW9xqvSsCRcJ5FtI/WoTT7USan4njgs+8JA4ZyHKj iwuIyWpNU2DO4hM2T5SyuL1ws7POBgrIhW/f6wIJXC6O3n55q9T7+EyIKDWLrFCgHZ1W uCesIeGLWIhegYszyYowsRHof25JrrQCo4tuUYjwVYHMMXpD4CBPMkxCD3bIDCVcRsFR 12TwPqZZqO4CkGnKgzLFvE1KKCFUbU/5oMqphEPaO7RZQ5MkqJOgVejiHaBlfWsmztaK 4yCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=aItUdumH08JU6N8OYOV8D532i+X0/mImH0WhN/CrnmQ=; b=gJcz8iT4hlTlQhdUmaksprAu7OPvaRyTWRP7TIjoJJubnzl/OffAhCxVPKJYNPfCaj nhbYwsiUibdF1jti5dqvm1hBCANwZbdBHo6tyTPWjUEzfjwFCKQJW3UcI8StwG6L6mfv RgJnn+QQ6WboaQfOqWe3Qkx+NLAARERWi7ozsMGHqnO2RxXrLtxArhOX7CKg5V0o0eev 8r5gWgrVYw7qgq47sF3ubZfJMDZsSNcBLVz82xm690QM5I3IbW/UFCHFLq3DcR10DuH9 chMYuG558/BDlqxp1VidWDFD185COYiJhgWV6Me+9vat1nFgJht6+9qtm6N5dssv+lcl X2SA== X-Gm-Message-State: APzg51De02cZiDYahd3iOE6k7PBqb2NZqLlxzrl2l98oi9qg/Vq8Rfro 0oddqAhDv9HTvhWwLzcscp2whQ== X-Google-Smtp-Source: ANB0VdYxVtYoVrLMFEpDNs+uHYc7T91qwTwZrAmaELdHXLWpvvy0gfMQcbOKLYRI8ktpSF7pnCfWJQ== X-Received: by 2002:a17:902:42a3:: with SMTP id h32-v6mr10528882pld.105.1535316506776; Sun, 26 Aug 2018 13:48:26 -0700 (PDT) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id n79-v6sm21229406pfh.2.2018.08.26.13.48.26 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 26 Aug 2018 13:48:26 -0700 (PDT) Date: Sun, 26 Aug 2018 13:48:17 -0700 From: Stephen Hemminger To: "Wiles, Keith" Cc: waqas ahmed , "users@dpdk.org" Message-ID: <20180826134817.41e34dad@xeon-e3> In-Reply-To: References: <6E42D8F7-5E0D-4943-88F8-01A3F33AD0E6@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 20:48:28 -0000 On Sun, 26 Aug 2018 17:48:04 +0000 "Wiles, Keith" wrote: > > On Aug 26, 2018, at 12:38 PM, waqas ahmed wrote: > > > > 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. > > 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 > > > > > > 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 > > > > Regards, > Keith > DPDK is getting numa socket from sysfs. Make sure your kernel is compiled with NUMA support, and look at /sys/bus/pci/devices to check for numa_node file.