From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Doug Smythies" Subject: RE: [PATCH 1/1] intel_pstate: Increase hold-off time before busyness is scaled Date: Fri, 19 Feb 2016 08:38:41 -0800 Message-ID: <001501d16b33$ff61d200$fe257600$@net> References: <1455793883-14214-1-git-send-email-mgorman@techsingularity.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from cmta7.telus.net ([209.171.16.80]:55546 "EHLO cmta7.telus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1426821AbcBSQiq (ORCPT ); Fri, 19 Feb 2016 11:38:46 -0500 In-Reply-To: Content-Language: en-ca Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: 'Stephane Gasparini' , 'Mel Gorman' Cc: 'Rafael Wysocki' , 'Ingo Molnar' , 'Peter Zijlstra' , 'Matt Fleming' , 'Mike Galbraith' , 'Linux-PM' , 'LKML' , 'Srinivas Pandruvada' Hi Steph, On 2016.02.19 03:12 Stephane Gasparini wrote: > > The issue you are reporting looks like one we improved on android by using > the average pstate instead of using the last requested pstate > > We know that this is improving the ffmpeg encoding performance when using the > load algorithm. > > see patch attached > > This patch is only applied on get_target_pstate_use_cpu_load however you can give > it a try on get_target_pstate_use_performance Yes, that type of patch works on the load based approach. However, I do not think it works on the performance based approach. Why not? Well, and if I understand correctly, follow the math and you end up with: scaled_busy = 100% scaled_busy = (aperf * 100% / mperf) * (max_pstate / * ((aperf * max_pstate) / mperf)) ... Doug