All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: initialize ring frequency scaling table on SNB
Date: Wed, 22 Jun 2011 12:30:17 +0100	[thread overview]
Message-ID: <e0d58a$g0g3f@orsmga002.jf.intel.com> (raw)
In-Reply-To: <20110621152424.75f54a13@jbarnes-desktop>

On Tue, 21 Jun 2011 15:24:24 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> The ring frequency scaling table tells the PCU to treat certain GPU
> frequencies as if they were a given CPU frequency for purposes of
> scaling the ring frequency.  Normally the PCU will scale the ring
> frequency based on the CPU P-state, but with the table present, it will
> also take the GPU frequency into account.  The scaling_factor used in
> this patch may not be ideal, but is enough to increase performance in
> nexuiz on a 1366x768 panel by about 20%.

Am I right in thinking that the improvement offered by these new defaults
is dependent upon the previous values programmed by the BIOS? On my
desktop SNB, I only see a marginal improvement (<~1%) for games and
similarly small differences for cairo-gl/xlib.

Plus they also revealed my confusion over dev_priv->min_delay is actually
min_freq on SNB. Evil. :-p
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-06-22 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 22:24 [PATCH] drm/i915: initialize ring frequency scaling table on SNB Jesse Barnes
2011-06-22 11:30 ` Chris Wilson [this message]
2011-06-22 16:49   ` Jesse Barnes
2011-06-22 18:42 ` Eric Anholt
2011-06-22 19:55   ` Jesse Barnes
2011-06-22 19:56   ` Jesse Barnes
2011-06-23 17:11     ` Jesse Barnes
2011-06-23 20:08       ` Chris Wilson
2011-06-23 20:16         ` Jesse Barnes

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='e0d58a$g0g3f@orsmga002.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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.