From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) by dpdk.org (Postfix) with ESMTP id 81B046831 for ; Fri, 29 Nov 2013 11:52:46 +0100 (CET) Received: by mail-lb0-f174.google.com with SMTP id c11so6920079lbj.33 for ; Fri, 29 Nov 2013 02:53:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+02MxpSV1hOv0X7b/Unr9l2MjwZGQyeYpXxkJqM4PSQ=; b=FYGCCAFJGr5tydd1JamhcZJeTdg6Y9AbqZvQPoWqceUbfJCXH9gdSczp1uI0MeFl0j R0bmEeY4kH8JAuG4+KnXiKfqBDPJX51AsTXMtxWhSmn9dZ+WTR/Dk9LLBaqIIxkIGkQQ j5AuwnFYjDFs5HVbHnNcGV6trOTdm7VsCZjaPaOP1U9KpuMHUjlV81f6MYsz33keIGOc jfLLAEy2PZzCNIBE6C/2uYcpgQ2y9z7tuxjdrlgrf8thxBVBUZS4CQ3+u/ro+W3QMcwT 0VnZwPIBM5nRN8kZVmckdynKWzn6hMeKewZ9rUdK1wcsqGTAX7Gk6gc7IQaGx40nlgAF b5pA== X-Received: by 10.152.120.102 with SMTP id lb6mr1402341lab.37.1385722427017; Fri, 29 Nov 2013 02:53:47 -0800 (PST) Received: from [192.168.15.113] ([87.236.23.254]) by mx.google.com with ESMTPSA id r7sm52790538lbo.5.2013.11.29.02.53.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 29 Nov 2013 02:53:46 -0800 (PST) Message-ID: <52987236.3020707@gmail.com> Date: Fri, 29 Nov 2013 14:53:42 +0400 From: Dmitry Vyal User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: "Richardson, Bruce" , Thomas Monjalon References: <528F4E41.2000405@gmail.com> <201311221348.02307.thomas.monjalon@6wind.com> <5295FC76.70201@gmail.com> <201311271542.05288.thomas.monjalon@6wind.com> <59AF69C657FD0841A61C55336867B5B01A9781FC@IRSMSX103.ger.corp.intel.com> In-Reply-To: <59AF69C657FD0841A61C55336867B5B01A9781FC@IRSMSX103.ger.corp.intel.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Sporadic errors while initializing NICs in example applications, dpdk-1.5.0r1 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, 29 Nov 2013 10:52:46 -0000 Hmm, that's strange. I don't know how to interpret my observations then. I have access to two platforms, one is based on Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz and another on Intel(R) Xeon(R) CPU E3-1270 v3 @ 3.50GHz. Both running ubuntu-12.04 server. I see repeating errors on NIC initialisation phase. The error frequency greatly reduces if I patch loop limit as I described earlier or if I call rte_power_init and rte_power_freq_max as Thomas suggested. But the only way to get rid of them completely is to set performance governor. On 11/28/2013 03:01 PM, Richardson, Bruce wrote: >> It's probably due to a frequency scaling. >> The timer based is initialized when DPDK initialize and the CPU can change >> its frequency, breaking next timers. >> >> The fix is to control the CPU frequency. >> Please try this, without your patch: >> for g in /sys/devices/system/cpu/*/cpufreq/scaling_governor; do >> echo performance >$g; done The right fix for applications (examples and >> testpmd included) could be to call rte_power_init(). Patches are welcomed. >> > [BR] Frequency changes should not affect timers for modern Intel CPUs. Please see the " Intel(r) 64 and IA-32 Architectures Software Developer's Manual" Volume 3 (http://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-software-developer-system-programming-manual-325384.pdf) , Section 17.13 for more details on this. >