From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id B0A11684E for ; Tue, 16 Aug 2016 20:09:40 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id EDD10C8; Tue, 16 Aug 2016 11:09:39 -0700 (PDT) Date: Tue, 16 Aug 2016 11:09:39 -0700 From: Matthew Hall To: Stephen Hemminger Cc: Kevin Wilson , users@dpdk.org Message-ID: <20160816180939.GA27682@mhcomputing.net> References: <20160718191350.GB19151@mhcomputing.net> <20160816110526.144625fb@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160816110526.144625fb@xeon-e3> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [dpdk-users] Which coremask and "-n" (number of mem channels) should be used for a system with only "node1" (no "node0") and 2 sockets ? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Aug 2016 18:09:41 -0000 On Tue, Aug 16, 2016 at 11:05:26AM -0700, Stephen Hemminger wrote: > What if you have a two socket machine, and node 0 is not populated? I did include that possibility. But most NUMA systems I have set up myself will not boot if Socket 1 is full and Socket 0 is empty. The early boot code generally assumes Socket 0 is valid when first initting itself. > Also does the kernel have NUMA support enabled? Good question, the vast majority of standard SMP kernels do have NUMA at this point I believe. It would maybe be good to see if the issue went away if the machine was intentionally run with a UP kernel. > Long ago there was a bug in DPDK where it got NUMA socket info from > /proc/cpuinfo. On some machines, the 'physical id' starts at 1 because value > comes from BIOS. Ouch... that's very evil of the BIOS. But also sadly not surprising. Matthew.