From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by dpdk.org (Postfix) with ESMTP id 6A5D2684E for ; Tue, 16 Aug 2016 20:05:16 +0200 (CEST) Received: by mail-pa0-f54.google.com with SMTP id fi15so28546290pac.1 for ; Tue, 16 Aug 2016 11:05:16 -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=0VFpso6vNslCb4vcLIrC1FMz1lFV7yPReLcQJukv4Xk=; b=yY/x8/OcAU+23846fJnSvEVibaJPsVSGjpSa7gvGDLEa8AMnDU/oiHuPR7NfiD0mUp gw5hyYZ6i4GE88nPFdXVPPF6ukdQR7UyqzRGczU67dHpDe4V68dCalgh1uaRmEVHnLqL /cIKZShAqY8NleIWipQdD9XimuMyZ3cTBTRGWGagVXNeSzYZwyifZyr8JxNlPJpDcvKd HdbryIsRg2vx99yG1D9AoRevJo2a1KvJ+0y7yDySOUFp1JBK89nWbw0YGXy13A8mgc1A FMrOwg0VX9yKZll8juVJfTJ6RGrvQ0RPJh3y+tx+kmRj29OuxlYul7VHbnD9dRqyjro2 6/0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=0VFpso6vNslCb4vcLIrC1FMz1lFV7yPReLcQJukv4Xk=; b=MQp3RtOy0jvGzUzzOEPDz2KRgFoI8+Q9JP+wl0jcxIgh4qDFfrmt4EgGZ/ShLnIm48 0sHiLkmfOvuWtKZ3j+9vbB4kbmBVgimxbEVsTMcKZkWbqK5pfeiLa+1YpFb/JBsKoZem V6BqoBs4ylcDFWNFjdyNhjM85Q7WXym1RKoe02YpEwy3+mgBwV0ShDlVf7+B3TgGv7/s Laylzzy8s+Vrs8oB3RgJjAzWa0qpqlawnHIEqe1V6+h5ZcBflmoDbsTUjgtGKlGGad6j d+VDiQDdN1WCGjWbU3R+d5hfAz10TNEExN2IbNfFkmxPIKCXL440PbAR+xdspkk58YKs CWpQ== X-Gm-Message-State: AEkoouu1Ny2RHgb2dB7hRf+3ozJ3a3BwXI//I02FFx5FRne+G62agRBfOUdHmt4SkgTeEA== X-Received: by 10.66.49.137 with SMTP id u9mr67659178pan.72.1471370715725; Tue, 16 Aug 2016 11:05:15 -0700 (PDT) Received: from xeon-e3 (static-50-53-69-251.bvtn.or.frontiernet.net. [50.53.69.251]) by smtp.gmail.com with ESMTPSA id t80sm40953033pfj.38.2016.08.16.11.05.15 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 16 Aug 2016 11:05:15 -0700 (PDT) Date: Tue, 16 Aug 2016 11:05:26 -0700 From: Stephen Hemminger To: Kevin Wilson Cc: Matthew Hall , users@dpdk.org Message-ID: <20160816110526.144625fb@xeon-e3> In-Reply-To: References: <20160718191350.GB19151@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:05:16 -0000 On Tue, 16 Aug 2016 20:41:42 +0300 Kevin Wilson wrote: > Thanks Metthew. > Indeed, something seems broken in that machine, > > Running > dmidecode > gives: > ..... > Invalid entry length (0). DMI table is broken! Stop > > Kevin > > > On Mon, Jul 18, 2016 at 10:13 PM, Matthew Hall wrote: > > On Fri, Jul 15, 2016 at 09:51:42AM +0300, Kevin Wilson wrote: > >> Hello, > >> I have a machine on which there is a bit non common setup: I have only > >> "node1" (no node0) under /sys/devices/system/node: > >> ls /sys/devices/system/node/ > >> ... > >> node1 > >> ... > > > > If I had to guess then either the BIOS is busted or the CPU is in the wrong > > socket or the RAM is in the wrong socket. > > > > Either way all bets are off how this is going to pan out. Probably badly when > > it comes to getting the top performance. > > > > Some exploration of the dmidecode output on the machine could be valuable. > > > > Matthew. What if you have a two socket machine, and node 0 is not populated? Also does the kernel have NUMA support enabled? 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.