From: "Szwichtenberg, Radoslaw" <radoslaw.szwichtenberg@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Subject: Re: [PATCH 3/3] drm/i915: Only apply the jump to the "efficient RPS" frequency on startup
Date: Tue, 14 Feb 2017 16:19:15 +0000 [thread overview]
Message-ID: <1487089152.14524.3.camel@intel.com> (raw)
In-Reply-To: <20170210150348.22146-3-chris@chris-wilson.co.uk>
On Fri, 2017-02-10 at 15:03 +0000, Chris Wilson wrote:
> Currently we apply the jump to rpe if we are below it and the GPU needs
> more power. For some GPUs, the rpe is 75% of the maximum range causing
> us to dramatically overshoot low power applications *and* unable to
> reach the low frequency that can most efficiently deliver their
> workload.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Radoslaw Szwichtenberg <radoslaw.szwichtenberg@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-14 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:03 [PATCH 1/3] drm/i915: Enable fine-tuned RPS for cherryview Chris Wilson
2017-02-10 15:03 ` [PATCH 2/3] drm/i915: Don't accidentally increase the frequency in handling DOWN rps Chris Wilson
2017-02-14 15:25 ` Szwichtenberg, Radoslaw
2017-02-10 15:03 ` [PATCH 3/3] drm/i915: Only apply the jump to the "efficient RPS" frequency on startup Chris Wilson
2017-02-14 16:19 ` Szwichtenberg, Radoslaw [this message]
2017-02-10 17:52 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] drm/i915: Enable fine-tuned RPS for cherryview Patchwork
2017-02-10 22:52 ` ✓ Fi.CI.BAT: success " Patchwork
2017-02-14 22:38 ` Chris Wilson
2017-02-14 15:28 ` [PATCH 1/3] " Szwichtenberg, Radoslaw
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=1487089152.14524.3.camel@intel.com \
--to=radoslaw.szwichtenberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.