From: Eero Tamminen <eero.t.tamminen@intel.com>
To: Jesse Barnes <jesse.barnes@intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Restore waitboost credit to the synchronous waiter
Date: Tue, 08 Dec 2015 10:35:56 +0200 [thread overview]
Message-ID: <5666966C.5060101@intel.com> (raw)
In-Reply-To: <5665C423.6000907@intel.com>
Hi,
On 12/07/2015 07:38 PM, Jesse Barnes wrote:
[...]
> Still wishing we had a good way to benchmark these types of changes
> across a range of workloads. Eero, have you guys looked at turbo stuff
> at all yet?
Except for this, not really:
https://jira01.devtools.intel.com/browse/LCK-2271
To make results comparable other platforms, I'm using sustained
performance numbers by discarding results for first round(s) that were
run with turbo.
For some of performance tracks, we've also planned to disable power
management completely (e.g. by using fixed freqs for CPU & GPU) because
it causes way too much variance to performance results (more between
runs, than within single run).
- Eero
> Also, is the boost logic only documented in misc commit messages? Or do
> we have a nice block of text somewhere describing the intent (which may
> not match our implementation!) and how we try to achieve it?
>
> Those are both new requests though, so no need to block this patch:
> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-12-08 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 22:48 [PATCH] drm/i915: Restore waitboost credit to the synchronous waiter Chris Wilson
2015-12-07 17:38 ` Jesse Barnes
2015-12-08 8:35 ` Eero Tamminen [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=5666966C.5060101@intel.com \
--to=eero.t.tamminen@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jesse.barnes@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