From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by dpdk.org (Postfix) with ESMTP id DF73430E for ; Fri, 31 May 2013 18:55:52 +0200 (CEST) Received: by mail-we0-f182.google.com with SMTP id q57so1417199wes.41 for ; Fri, 31 May 2013 09:55:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=eLxkkKZCKYTHfE5wpHd4S6SeBPYMxIWdPU8q+TjFmCA=; b=EQSoc1pXdmIXc8U2FbB2ig5MYpaem7Oxhu6LDFxEmHCTDGTVGg2o/wAh0ngBT1V2l/ EaXtNzbX6jNVbQ+oLVCi+pvQ5TTTYPKwo15x+60FZJLZCuNfCQusgbgekPM8v6K9jp0c k5hfjnUHtucYvsl4SbmeCOPHN9LdurUnN7xz76xKDzpoClleWogv9s0kjYCF0+m6VSqR oSo/Pc9pz4b613CR7b3sDNqNPhVUmr+Agkvqm2sp1nZ5/bW9BvUSec80hNyqnwBcKkC1 nQ7r0gbZUewOLVdT1fG/m9WTC6O6S3QmavArpawMxpfXhtDGaUu0qHSQJJDRX1UFjIdS yGJg== X-Received: by 10.194.21.138 with SMTP id v10mr10401155wje.16.1370019359472; Fri, 31 May 2013 09:55:59 -0700 (PDT) Received: from [192.168.0.11] (mic92-3-81-56-67-82.fbx.proxad.net. [81.56.67.82]) by mx.google.com with ESMTPSA id fx7sm5137324wic.11.2013.05.31.09.55.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 09:55:58 -0700 (PDT) Message-ID: <51A8D353.50101@6wind.com> Date: Fri, 31 May 2013 18:44:03 +0200 From: Damien Millescamps Organization: 6WIND S.A. User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: dev@dpdk.org References: <20130530171234.301927271@vyatta.com> <51A86D65.2090003@6wind.com> <20130531084529.5c63d4c0@nehalam.linuxnetplumber.net> In-Reply-To: <20130531084529.5c63d4c0@nehalam.linuxnetplumber.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQlLXyFLHOyQcRux3ehUAUDJ02FFvFcRn75CsZ4pSa/oUVUYGDwESF4QJ/nlI5SFk0Um4AWf 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 16:55:53 -0000 On 05/31/2013 05:45 PM, Stephen Hemminger wrote: > This was confirmed by several kernel developers including Andi Kleen from > Intel. The value in /proc/cpuinfo comes from the APCI tables and is the value > reported by the BIOS. There are machines that report socket 1 and 2. > Haven't played with older kernels, but the topology information in sysfs > has existed since 2.6.16. Hi Stephen, You didn't really address my point, because the Linux documentation says something doesn't mean it works in the real world. If you take the example of the hugepages, they have been in the Linux kernel since 2.6.28, but the last fix was pushed in 2.6.37 and before 2.6.33 it is just impossible to do something with hugepages. If you take a look at section 2.3.2 of the DPDK getting started: http://www.intel.com/content/dam/www/public/us/en/documents/guides/intel-dpdk-getting-started-guide.pdf, you will find that this issue is at least partially addressed. So the point is that the topology information being theoretically correct on all kernel Linux supported by the DPDK, but the information being practically wrong on versions prior to kernel 3.3 means that the "fix" is breaking the support for a quite huge range of kernel versions... So maybe there might be a better way to get this node information on all kernel still currently supported by the DPDK. Cheers, -- Damien Millescamps