From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1428267AbcBSQis (ORCPT ); Fri, 19 Feb 2016 11:38:48 -0500 Received: from cmta7.telus.net ([209.171.16.80]:55545 "EHLO cmta7.telus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1426458AbcBSQiq (ORCPT ); Fri, 19 Feb 2016 11:38:46 -0500 X-Authority-Analysis: v=2.1 cv=fqshHwMf c=1 sm=2 tr=0 a=zJWegnE7BH9C0Gl4FFgQyA==:117 a=zJWegnE7BH9C0Gl4FFgQyA==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=Pyq9K9CWowscuQLKlpiwfMBGOR0=:19 a=IkcTkHD0fZMA:10 a=2y8WAHZXoZ1ZGKcvVGsA:9 a=QEXdDO2ut3YA:10 X-Telus-Outbound-IP: 173.180.45.4 From: "Doug Smythies" To: "'Stephane Gasparini'" , "'Mel Gorman'" Cc: "'Rafael Wysocki'" , "'Ingo Molnar'" , "'Peter Zijlstra'" , "'Matt Fleming'" , "'Mike Galbraith'" , "'Linux-PM'" , "'LKML'" , "'Srinivas Pandruvada'" References: <1455793883-14214-1-git-send-email-mgorman@techsingularity.net> In-Reply-To: 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> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdFrBlbCYB9SrJToTnSUHyK9PsMRlQAKOinQ Content-Language: en-ca Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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