From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751212AbcBLHZZ (ORCPT ); Fri, 12 Feb 2016 02:25:25 -0500 Received: from cmta4.telus.net ([209.171.16.77]:52495 "EHLO cmta4.telus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751083AbcBLHZX (ORCPT ); Fri, 12 Feb 2016 02:25:23 -0500 X-Authority-Analysis: v=2.1 cv=TLK4MARa 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=zkm1L8tsJ9XMyw1yhtwA:9 a=QEXdDO2ut3YA:10 X-Telus-Outbound-IP: 173.180.45.4 From: "Doug Smythies" To: "'Rafael J. Wysocki'" , "'Srinivas Pandruvada'" Cc: "'Linux PM list'" , "'Ingo Molnar'" , "'Linux Kernel Mailing List'" , "'Peter Zijlstra'" , "'Viresh Kumar'" , "'Juri Lelli'" , "'Steve Muckle'" , "'Thomas Gleixner'" References: <3071836.JbNxX8hU6x@vostro.rjw.lan> <2111826.yKEUOzphHC@vostro.rjw.lan> <008201d16458$69b2a4f0$3d17eed0$@net> <7442347.PCmPlrAvBe@vostro.rjw.lan> <002101d1651e$8ff027c0$afd07740$@net> In-Reply-To: <002101d1651e$8ff027c0$afd07740$@net> Subject: RE: [PATCH v6 0/3] cpufreq: Replace timers with utilization update callbacks Date: Thu, 11 Feb 2016 23:25:18 -0800 Message-ID: <002601d16566$88455610$98d00230$@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: AdFkWRZVwGPBO7ciTCK/05pIE6dyawAl7OKQABzJT8A= Content-Language: en-ca Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016.02.11 14:50 Doug Smythies wrote: > On 2016.02.10 22:03 Srinivas Pandruvada wrote: >> On Wednesday, February 10, 2016 03:11:43 PM Doug Smythies wrote: >>> My test computer has an older model i7 (Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz) >> Thanks Doug. If you have specific workloads, please compare performance. > My work so far has been testing functionality, with unrealistic workloads specifically > designed to exaggerate issues, in this case the duration problem. > > I'll look at some real world workload scenarios. Turbostat used for package power, starts before Phoronix tests starts, and ends after Phoronix test ends. Control Sample: Kernel 4.5-rc3: Phoronix ffmpeg: turbostat 180 Sec. 12.07 Sec. Ave. 27.14 Watts. Phoronix apache: turbostat 200 Sec. 19797.0 R.P.S. Ave. 34.01 Watts. Phoronix kernel: turbostat 180 Sec. 139.93 Sec. 49.09 Watts. Phoronix Postmark (Disk Test): turbostat 200 Sec. 5813 T.P.S. Ave. 21.33 Watts. Kernel 4.5-rc3 + RJW 3 patch set version 7: Phoronix ffmpeg: turbostat 180 Sec. 11.67 Sec. Ave. 27.35 Watts. Phoronix apache: turbostat 200 Sec. 19430.7 R.P.S. Ave. 34.18 Watts. Phoronix kernel: turbostat 180 Sec. 139.81 Sec. 48.80 Watts. Phoronix Postmark (Disk Test): turbostat 200 Sec. 5683 T.P.S. Ave. 22.41 Watts. ... Doug