From owner-freebsd-bugs@freebsd.org Thu May 11 18:01:27 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 025DAD68261 for ; Thu, 11 May 2017 18:01:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CC9C31208 for ; Thu, 11 May 2017 18:01:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4BI1QUa097695 for ; Thu, 11 May 2017 18:01:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219213] powerd causing problems with ryzen Date: Thu, 11 May 2017 18:01:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: shitman71@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 May 2017 18:01:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219213 --- Comment #1 from SF --- To be more specific about power-saving features: CPU's have different p-states since a long time now but powerd only knows 3 options to set: adaptive, maximum, minimum I have only 2 options for the adaptive-mode to set percentages for minimum = and maximum. I dont know how many different p-state each CPU has but there is definitely more then just maximum and minimum. I remember 4-5 different p-states with = my old Phenom X6 1100T(cpu from 2010) i had before. Your powerd is very primitive and i think it doesnt fit todays demands of flexible power-management and accurate delivery of performance. With 4-5 p-states i can set 4-5 barriers to hit to get my CPU more precisely onto its needed level. With todays CPU-Performance i can do more math to calculate its needed p-st= ate. An Ryzen R7 1700X has 16 CPU-Cores, there is easyly some spare calculation-power to do the math for adjusting the p-states more accurate. e.x.: 1 primary interval(long time period) 1 secondary interval(short time period) which gets launched from the primary interval after the specified time 1 counter for each p-state-limit The primvary interval kicks in each 15 seconds. The secondary interval checks every 40ms the average cpu-load for an durati= on of 1 second. It increases the counter for the assigned p-state at each check until the 1 second duration is finished. It selects the p-state with the highest counter and priority. Shouldn't be too hard? --=20 You are receiving this mail because: You are the assignee for the bug.=