From: "Sun, Daisy" <daisy.sun@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/bdw: BDW Software Turbo
Date: Thu, 10 Jul 2014 19:39:32 -0700 [thread overview]
Message-ID: <53BF4E64.2040802@intel.com> (raw)
In-Reply-To: <20140710190754.GN8986@nuc-i3427.alporthouse.com>
This Software turbo will mainly take place of the hardware driven
interrupt part without touching the boost/idle strategy.
So gen6_rps_boost and gen6_rps_idle will still function for BDW.
I can revise the commit message to clarify.
On 7/10/2014 12:07 PM, Chris Wilson wrote:
> On Thu, Jul 10, 2014 at 11:42:59AM -0700, Sun, Daisy wrote:
>> GT is not going to run at a single frequency all the time actually.
>> It starts from a single frequency, and then will dynamically adjust
>> according to the GT utilization, either go up or down.
>> From this perspective, SW turbo function the same as the HW turbo.
> Urm, read your code again.
>
>> For the algorithm, we did go over the design forum before implementation.
>> What kind of improvement is expected? Please let me know if any
>> important case is not taken into account. Thanks.
> You have no faststart or boost strategy, so typical desktop usage will
> feel very laggy. For a large number of use cases you never change
> freequency.
> -Chris
>
next prev parent reply other threads:[~2014-07-11 2:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 1:00 [PATCH v2] drm/i915/bdw: BDW Software Turbo Daisy Sun
2014-07-10 8:32 ` Chris Wilson
2014-07-10 18:42 ` Sun, Daisy
2014-07-10 19:07 ` Chris Wilson
2014-07-11 2:39 ` Sun, Daisy [this message]
2014-07-11 6:15 ` Chris Wilson
2014-07-14 4:22 ` Sun, Daisy
2014-07-14 6:59 ` Daniel Vetter
2014-07-14 7:03 ` Daniel Vetter
2014-07-15 6:35 ` Sun, Daisy
2014-07-24 20:28 ` Jesse Barnes
2014-07-25 7:22 ` Daniel Vetter
2014-07-25 15:51 ` Sun, Daisy
2014-07-26 0:47 ` Sun, Daisy
2014-07-28 9:17 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53BF4E64.2040802@intel.com \
--to=daisy.sun@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox