From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/gt: Try to smooth RPS spikes
Date: Wed, 15 Apr 2020 13:56:59 +0300 [thread overview]
Message-ID: <20200415105659.GA50947@intel.intel> (raw)
In-Reply-To: <20200414161423.23830-1-chris@chris-wilson.co.uk>
Hi Chris,
On Tue, Apr 14, 2020 at 05:14:22PM +0100, Chris Wilson wrote:
> By the time we respond to the RPS interrupt [inside a worker], the GPU
> may be running a different workload. As we look to make the evalution
> intervals shorter, these spikes are more likely to okay. Let's try to
> smooth over the spikes in the workload by comparing the EI interrupt
> [up/down events] with the most recently completed EI; if both say up,
> then increase the clocks, if they disagree stay the same. In principle,
> this means we now take 2 up EI to go increase into the next bin, and
> similary 2 down EI to decrease. However, if the worker runs fast enough,
> the previous EI in the registers will be the same as triggered the
> interrupt, so responsiveness remains unaffect. [Under the current scheme
> where EI are on the order of 10ms, it is likely that this is true and we
> compare the interrupt with the EI that caused it.]
looks reasonable to me. Wouldn't it make also sense to evaluate
the difference between the current and the previous pm_iir?
Reviewed-by: Andi Shyti <andi.shyti@inte.com>
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-04-15 10:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 16:14 [Intel-gfx] [PATCH 1/2] drm/i915/gt: Try to smooth RPS spikes Chris Wilson
2020-04-14 16:14 ` [Intel-gfx] [PATCH 2/2] drm/i915/gt: Shrink the RPS evalution intervals Chris Wilson
2020-04-14 16:14 ` Chris Wilson
2020-04-14 16:35 ` [Intel-gfx] " Chris Wilson
2020-04-14 16:35 ` Chris Wilson
2020-04-14 19:39 ` [Intel-gfx] " Francisco Jerez
2020-04-14 19:39 ` Francisco Jerez
2020-04-14 20:13 ` [Intel-gfx] " Chris Wilson
2020-04-14 20:13 ` Chris Wilson
2020-04-14 21:00 ` Francisco Jerez
2020-04-14 21:00 ` Francisco Jerez
2020-04-14 21:52 ` Chris Wilson
2020-04-14 21:52 ` Chris Wilson
2020-04-14 22:28 ` Francisco Jerez
2020-04-14 22:28 ` Francisco Jerez
2020-04-14 22:38 ` Francisco Jerez
2020-04-14 22:38 ` Francisco Jerez
2020-04-14 21:35 ` Chris Wilson
2020-04-14 21:35 ` Chris Wilson
2020-04-14 22:27 ` Francisco Jerez
2020-04-14 22:27 ` Francisco Jerez
2020-04-15 7:37 ` Chris Wilson
2020-04-15 7:37 ` Chris Wilson
2020-04-15 11:36 ` Chris Wilson
2020-04-15 11:36 ` Chris Wilson
2020-04-15 11:11 ` Andi Shyti
2020-04-15 11:11 ` Andi Shyti
2020-04-15 0:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/gt: Try to smooth RPS spikes Patchwork
2020-04-15 1:13 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2020-04-15 1:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-04-15 10:56 ` Andi Shyti [this message]
2020-04-15 11:24 ` [Intel-gfx] [PATCH 1/2] " Chris Wilson
2020-04-15 11:45 ` Chris Wilson
2020-04-15 15:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for series starting with [1/2] " Patchwork
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=20200415105659.GA50947@intel.intel \
--to=andi.shyti@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.