From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Zhang, Ouping" <ouping.zhang@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Increase the RC6p threshold.
Date: Mon, 25 Feb 2013 08:13:32 -0800 [thread overview]
Message-ID: <20130225081332.499c8609@jbarnes-desktop> (raw)
In-Reply-To: <AD7688D9264EBF4F8769FC633B3E3E8E23BCDC93@SHSMSX102.ccr.corp.intel.com>
How does the watt-hour result compare to before the patch?
Thanks,
Jesse
On Mon, 25 Feb 2013 07:33:38 +0000
"Zhang, Ouping" <ouping.zhang@intel.com> wrote:
> running video workload, video avg watt = 38.4 and watt-hour = 6.9
> cat /sys/class/drm/card0/power/rc6_residency_ms
> cat /sys/class/drm/card0/power/rc6p_residency_ms
> rc6_residency_ms increase from 6708 to 483627
> rc6p_residency_ms increase from 410092 to 423378
>
> -----Original Message-----
> From: Jesse Barnes [mailto:jbarnes@virtuousgeek.org]
> Sent: Friday, February 22, 2013 12:50 AM
> To: Zhang, Ouping
> Cc: Stéphane Marchesin; intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATCH] drm/i915: Increase the RC6p threshold.
>
> You have to modify the kernel to make the change Stephane suggested, then measure the energy consumption across your workloads. I'd expect the residency to change, but I'm ultimately concerned with the energy used.
>
> Jesse
>
> On Thu, 21 Feb 2013 05:08:10 +0000
> "Zhang, Ouping" <ouping.zhang@intel.com> wrote:
>
> > Hi Jesse,
> >
> > Do you mean increase /sys/class/drm/card0/power/rc6p_residency_ms from 100000 to 150000, and measure power difference on IVB when system is on idle?
> >
> > -----Original Message-----
> > From: Jesse Barnes [mailto:jbarnes@virtuousgeek.org]
> > Sent: Wednesday, February 20, 2013 8:16 AM
> > To: Stéphane Marchesin
> > Cc: intel-gfx@lists.freedesktop.org; Zhang, Ouping
> > Subject: Re: [Intel-gfx] [PATCH] drm/i915: Increase the RC6p threshold.
> >
> > On Tue, 19 Feb 2013 15:53:56 -0800
> > Stéphane Marchesin <marcheu@chromium.org> wrote:
> >
> > > On Tue, Jan 29, 2013 at 7:41 PM, Stéphane Marchesin <marcheu@chromium.org>wrote:
> > >
> > > > This increases GEN6_RC6p_THRESHOLD from 100000 to 150000. For some
> > > > reason this avoids the gen6_gt_check_fifodbg.isra warnings and
> > > > associated GPU lockups, which makes my ivy bridge machine stable.
> > > >
> > > >
> > > Ping?
> >
> > Seems ok to me. Ouping, can you measure any power difference between the two values?
> >
> > Thanks,
> > --
> > Jesse Barnes, Intel Open Source Technology Center
>
>
> --
> Jesse Barnes, Intel Open Source Technology Center
--
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2013-02-25 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 3:41 [PATCH] drm/i915: Increase the RC6p threshold Stéphane Marchesin
2013-02-19 23:53 ` Stéphane Marchesin
2013-02-20 0:15 ` Jesse Barnes
2013-02-21 5:08 ` Zhang, Ouping
2013-02-21 16:49 ` Jesse Barnes
2013-02-25 7:33 ` Zhang, Ouping
2013-02-25 16:13 ` Jesse Barnes [this message]
2013-02-27 5:50 ` Zhang, Ouping
2013-02-27 16:23 ` Jesse Barnes
2013-03-05 9:02 ` 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=20130225081332.499c8609@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ouping.zhang@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