From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) by dpdk.org (Postfix) with ESMTP id 6FA9E30E for ; Fri, 31 May 2013 11:29:22 +0200 (CEST) Received: by mail-ea0-f177.google.com with SMTP id q14so1346525eaj.36 for ; Fri, 31 May 2013 02:29:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=KBePofjQXTa5ncgJ9Qczf+2I6JmO+RulHaUPFB64FmU=; b=JiCsXRe7ky06dZz+EEVwrWosXBOKRZt1owi47RahNMIKd55CGFBm3Zmo2eIGHdp2dn 7NgMX4bliW0o86Qn7r+WsDohgXOIfLhEMfVtyOwRIHNPNEYI46gx4m+w/lOm1u9yA7il RTIZD9VDNtYwdqihiAH3DrkAfjecQGff3gKCXLjdx5r2t62tRXNuUpoS4QbQRzin1ggu qyNIFPS9SRrr3VXPIkbJelVzi3dZNfoN43mhqGF1qDi4+FSfGW6tuXjcaCR4428yp2j9 g0+KCSo/NqOKs9D2w78AYyw5FYIgsqCBs6vf6/cDGTKA6LTP/CWygVENHQkBSGfEOSTo hZnQ== X-Received: by 10.14.7.198 with SMTP id 46mr12918758eep.17.1369992567708; Fri, 31 May 2013 02:29:27 -0700 (PDT) Received: from [10.16.0.97] (6wind.net2.nerim.net. [213.41.180.237]) by mx.google.com with ESMTPSA id e1sm31335890eem.10.2013.05.31.02.29.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 02:29:26 -0700 (PDT) Message-ID: <51A86D65.2090003@6wind.com> Date: Fri, 31 May 2013 11:29:09 +0200 From: Damien Millescamps User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9 MIME-Version: 1.0 To: dev@dpdk.org References: <20130530171234.301927271@vyatta.com> In-Reply-To: <20130530171234.301927271@vyatta.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnWPF0JK2UouzQ39O7q2wIHFfGmn/QHOn17M3xRTNA5GdjEopShZzVdf8rYb0hOuMx3Ne1E Subject: Re: [dpdk-dev] [PATCH 0/7] Vyatta patches X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 09:29:22 -0000 On 05/30/2013 07:12 PM, Stephen Hemminger wrote: > One fix not included is the NUMA cpu assignment. The original Intel code > in 1.2 incorrectly used /proc/cpuinfo to try and assign CPU's to NUMA socket. > The problem is that /proc/cpuinfo physical_id corresponds to what the BIOS > tells the kernel and is intended for messages only. For example, on our > Dell boxes the first CPU and only CPU is reported as physical_id 1! > The fix is to use sysfs instead, Hi Stephen, Are you using the /sys/devices/system/node/nodeX/cpuX/topology/physical_package_id special file ? If so, then it is only usable starting from Kernel 3.3 according to this fix: http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=64be4c1c2428e148de6081af235e2418e6a66dda The value returned for kernel prior to 3.3 is really not better than the one from /proc/cpuinfo, so that's kind of a robbing Peter to pay Paul example... There is obviously a problem with the NUMA node ID detection right now since both /proc/cpuinfo and /sys can return incorrect values, however the node and cpu numbering is always good in the kernel boot log from what I know. So there might be a better way to find the real node ID whatever the kernel version used. Cheers, -- Damien Millescamps