public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Kamble, Sagar A" <sagar.a.kamble@intel.com>
To: "Szwichtenberg, Radoslaw" <radoslaw.szwichtenberg@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Cc: "S, Deepak" <deepak.s@intel.com>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	"Goel, Akash" <akash.goel@intel.com>
Subject: Re: Why idle_freq is set to RPn and not RPe
Date: Wed, 30 Dec 2015 16:09:46 +0530	[thread overview]
Message-ID: <5683B472.1000309@intel.com> (raw)
In-Reply-To: <17D64081036A3D43BA31B5EA9AE8F54A4676DF7F@IRSMSX108.ger.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1704 bytes --]

Turbo frequency range is Rpe to Rp0 when GPU is active as, on workload 
submission frequency is taken to Rpe.

Does the HW require us to drop to RPn before entering RC6?
If we can enter RC6 even with other frequencies I think we can keep 
running at Rpe on Idle.

Only benefit of running at Rpn might be some additional power saving 
when workload is very lightweight. Is that correct Chris?


Thanks
Sagar



On 12/30/2015 3:20 PM, Szwichtenberg, Radoslaw wrote:
> Hello Chris!
>
> The question is: why this change in behavior was made?
>
> On previous platforms Gfx Turbo frequency selection range in driver was in between Rpe & Rp0. Since Rpe is the possible Fmax at Vmin, it was used as the starting frequency once driver booted and any value lower than that was not requested.
>
> Thanks!
> Radek
>
>> -----Original Message-----
>> From: Chris Wilson [mailto:chris@chris-wilson.co.uk]
>> Sent: Wednesday, December 30, 2015 10:31 AM
>> To: Kamble, Sagar A
>> Cc: S, Deepak; Szwichtenberg, Radoslaw; Intel Graphics Development; Goel,
>> Akash
>> Subject: Re: Why idle_freq is set to RPn and not RPe
>>
>> On Wed, Dec 30, 2015 at 02:51:27PM +0530, Kamble, Sagar A wrote:
>>> Hi Chris,
>>>
>>> With below commit, idle frequency is made RPn (HW Min).
>>> Why are we not keeping it at RPe (Efficient Frequency)?
>>> My understanding was to set Rpe on idle so that when GPU is out of
>>> RC6 it can start operating at efficient frequency.
>> The driver is *idle*. When there is work to be submitted to the GPU, then
>> we go back to RPe (though we wait for it to wake up first). RPe is just an
>> inflexion point on the power curve.
>> -Chris
>>
>> --
>> Chris Wilson, Intel Open Source Technology Centre


[-- Attachment #1.2: Type: text/html, Size: 4509 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2015-12-30 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30  9:21 Why idle_freq is set to RPn and not RPe Kamble, Sagar A
2015-12-30  9:31 ` Chris Wilson
2015-12-30  9:50   ` Szwichtenberg, Radoslaw
2015-12-30 10:00     ` Chris Wilson
2015-12-30 10:39     ` Kamble, Sagar A [this message]
2015-12-30 10:50       ` Chris Wilson
2015-12-31 17:38         ` Kamble, Sagar A
2016-01-05 16:51           ` Szwichtenberg, Radoslaw
2016-01-05 20:54             ` Chris Wilson

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=5683B472.1000309@intel.com \
    --to=sagar.a.kamble@intel.com \
    --cc=akash.goel@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=deepak.s@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=radoslaw.szwichtenberg@intel.com \
    /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