From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from fiji.vyatta.com (fiji.vyatta.com [76.74.103.50]) by dpdk.org (Postfix) with ESMTP id 0AC5730E for ; Thu, 30 May 2013 19:21:28 +0200 (CEST) Received: by fiji.vyatta.com (Postfix, from userid 1051) id A1DA9B24002; Thu, 30 May 2013 08:08:24 -0700 (PDT) Message-Id: <20130530171234.301927271@vyatta.com> User-Agent: quilt/0.60-1 Date: Thu, 30 May 2013 10:12:34 -0700 From: Stephen Hemminger To: dev@dpdk.org X-Mailman-Approved-At: Thu, 30 May 2013 23:34:04 +0200 Subject: [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: Thu, 30 May 2013 17:21:28 -0000 This is a subset of the Vyatta patches we use. They include some bug fixes and simple changes to make life easier. 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, and Intel did incorporate my fix in the next DPDK version, and don't want to confuse this code base by putting in a conflicting change.