From: Ben Widawsky <ben@bwidawsk.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: re-enable rc6 for ironlake
Date: Thu, 28 Apr 2011 10:10:22 -0700 [thread overview]
Message-ID: <20110428171022.GA8967@bwgnt.jf.intel.com> (raw)
In-Reply-To: <20110427154940.6d7fa9a4@jbarnes-vaio.home>
On Wed, Apr 27, 2011 at 03:49:40PM -0700, Jesse Barnes wrote:
> On Wed, 27 Apr 2011 23:03:14 +0100
> Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > > We should probably just enable fbc on the pipe connected to the
> > > internal panel (if any) and keep it disabled otherwise.
> >
> > On Arrandale, fbc is potentially a bigger win than rc6 - but is also a
> > potential loss - right?
>
> No, I think rc6 is still a much bigger win even on Arrandale (iirc >>1W
> for rc6, ~0.5W for fbc best case). And yeah, there is the potential for
> increased power consumption when fbc is enabled if a framebuffer that
> doesn't compress very well continues to get re-compressed over a long
> period of time.
>
> Jesse
The last tests that I ran it seemed we needed to be really careful about
when to turn on FBC on for Arrandale as noted in the bug that Chris
assigned to me below :). I did some rc6 tests prior to the FBC tests and
can't find my notes, but I actually recall it being closer to 2W.
https://bugs.freedesktop.org/show_bug.cgi?id=31742
Ben
prev parent reply other threads:[~2011-04-28 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 23:12 [PATCH 0/4] Re-enable RC6 on Ironlake Ben Widawsky
2011-03-18 23:12 ` [PATCH 1/4] drm/i915: fix ilk rc6 teardown locking Ben Widawsky
2011-03-19 7:44 ` Chris Wilson
2011-03-19 18:38 ` [PATCH v2 " Ben Widawsky
2011-03-19 18:46 ` [PATCH " Keith Packard
2011-03-20 1:14 ` [PATCH v2 1/5] " Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 2/5] drm/1915: ringbuffer wait for idle function Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 3/5] drm/i915: fix rc6 initialization on Ironlake Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 4/5] drm/i915: debugfs for context information Ben Widawsky
2011-03-20 1:14 ` [PATCH v2 5/5] drm/i915: re-enable rc6 for ironlake Ben Widawsky
2011-03-18 23:12 ` [PATCH 2/4] drm/i915: fix rc6 initialization on Ironlake Ben Widawsky
2011-03-19 7:55 ` Chris Wilson
2011-03-20 0:07 ` Ben Widawsky
2011-03-18 23:12 ` [PATCH 3/4] drm/i915: debugfs for context information Ben Widawsky
2011-03-18 23:12 ` [PATCH 4/4] drm/i915: re-enable rc6 for ironlake Ben Widawsky
2011-04-27 7:49 ` Chris Wilson
2011-04-27 21:20 ` Jesse Barnes
2011-04-27 22:03 ` Chris Wilson
2011-04-27 22:49 ` Jesse Barnes
2011-04-28 17:10 ` Ben Widawsky [this message]
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=20110428171022.GA8967@bwgnt.jf.intel.com \
--to=ben@bwidawsk.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).