From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id 5B0459231 for ; Sun, 6 Dec 2015 01:08:40 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id CFA08324; Sat, 5 Dec 2015 19:08:39 -0500 (EST) Date: Sat, 5 Dec 2015 19:08:39 -0500 From: Matthew Hall To: dev@dpdk.org Message-ID: <20151206000839.GA23450@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [dpdk-dev] librte_power w/ intel_pstate cpufreq governor 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: Sun, 06 Dec 2015 00:08:40 -0000 Hello all, I wanted to ask some questions about librte_power and the great adaptive polling / IRQ mode example in l3fwd-power. I am very interested in getting this to work in my project because it will make it much friendlier to attract new community developers if I am as cooperative as possible with system resources. Let's discuss the init process for a moment. It has some problems on my system, and I need some help to figure out how to handle this right. 1. Begins with the call to rte_power_init. 2. Attempts to init ACPI cpufreq mode. 2.1. Sets lcore cpufreq governor to userspace mode. 2.2. Function power_get_available_freqs checks lcore CPU frequencies from: /sys/devices/system/cpu/cpuX/cpufreq/scaling_available_frequencies 2.3. This fails with (cryptic) error "POWER: ERR: File not openned". I am planning to write a patch for this error a bit later. My kernel is using the intel_pstate driver, so scaling_available_frequencies does not exist: http://askubuntu.com/questions/544266/why-are-missing-the-frequency-options-on-cpufreq-utils-indicator 3. When power_get_available_freqs fails, rte_power_acpi_cpufreq_init fails. 4. rte_power_init will try rte_power_kvm_vm_init. That will fail because it's a physical Skylake system not some kind of VM. 5. Now rte_power_init totally fails, with error "POWER: ERR: Unable to set Power Management Environment for lcore 0". So, I have a couple of questions to figure out from here: 1. It seems bad to switch the governor into userspace before verifying the frequencies available in scaling_available_frequencies. If there are no frequencies available, it seems like it should not be trying to take over control of an effectively uncontrollable value. 2. If the governor is switched to userspace, and then no governing is done, it seems like the clockrate will necessarily always be wrong also because nothing will be configuring it anymore, neither kernel, nor failed DPDK userspace code, since rte_power_freq_up / down function pointers will always be NULL. Is this true? This seems bad if so. It seems that the librte_power code is basically out of date, as pstate has been present since Sandy Bridge, which is quite old by now for network processing. I am not sure how to make this work right now. So far I see a couple options but I really don't know much about this stuff: 1) skip rte_power_init completely, and let intel_pstate handle it using HWP mode 2) disable intel_pstate, switch to the legacy ACPI cpufreq (but people warned this old driver is mostly a no-op and the CPU ignores its frequency requests). The Internet advice says it's possible, but not a very good idea, to switch from the modern intel_pstate driver to the legacy ACPI mode. Reading through the kernel docs (below) state that it's better to use HWP (Hardware P State) mode: https://www.kernel.org/doc/Documentation/cpu-freq/intel-pstate.txt If none of this rte_power_init stuff works, are the other CPU conservation measures inside the l3fwd-power example enough to work right with HWP all by themselves with nothing additional? Thanks, Matthew.