drm/i915: Context aware user agnostic EU/Slice/Sub-slice control within kernel
This patch sets improves GPU power consumption on Linux kernel based OS such as
Chromium OS, Ubuntu, etc. Following are the power savings.
Power savings on GLK-GT1 Bobba platform running on Chrome OS.
-----------------------------------------------|
App /KPI | % Power Benefit (mW) |
------------------------|----------------------|
Hangout Call- 20 minute | 1.8% |
Youtube 4K VPB | 14.13% |
WebGL Aquarium | 13.76% |
Unity3D | 6.78% |
| |
------------------------|----------------------|
Chrome PLT | BatteryLife Improves |
| by ~45 minute |
-----------------------------------------------|
Power savings on KBL-GT3 running on Android and Ubuntu (Linux).
-----------------------------------------------|
App /KPI | % Power Benefit (mW) |
|----------------------|
| Android | Ubuntu |
------------------------|----------|-----------|
3D Mark (Ice storm) | 2.30% | N.A. |
TRex On screen | 2.49% | 2.97% |
Manhattan On screen | 3.11% | 4.90% |
Carchase On Screen | N.A. | 5.06% |
AnTuTu 6.1.4 | 3.42% | N.A. |
SynMark2 | N.A. | 1.7% |
-----------------------------------------------|
We have also observed GPU core residencies improves by 1.035%.
Technical Insights of the patch:
Current GPU configuration code for i915 does not allow us to change
EU/Slice/Sub-slice configuration dynamically. Its done only once while context
is created.
While particular graphics application is running, if we examine the command
requests from user space, we observe that command density is not consistent.
It means there is scope to change the graphics configuration dynamically even
while context is running actively. This patch series proposes the solution to
find the active pending load for all active context at given time and based on
that, dynamically perform graphics configuration for each context.
The feature can be enabled using sysfs. We examine pending
commands for a context in the queue, essentially, we intercept them before
they are executed by GPU and we update context with required number of EUs.
One questions, what's the right number of EUs?
Empirical data to achieve best performance in least power was considered.
For the later one, we roughly categorized number of EUs logically based on
platform. Now we compare number of pending commands with a particular threshold
and then set number of EUs accordingly with update context. That threshold
is also based on experiments & findings. If GPU is able to catch up with CPU,
typically there are no pending commands, the EU config would remain unchanged
there. In case there are more pending commands we reprogram context with higher
number of EUs.
Ankit Navik (3):
drm/i915: Get active pending request for given context
drm/i915: set optimum eu/slice/sub-slice configuration based on load
type
drm/i915: Predictive governor to control slice/subslice/eu
drivers/gpu/drm/i915/gem/i915_gem_context.c | 4 ++
drivers/gpu/drm/i915/gem/i915_gem_context_types.h | 37 +++++++++++
drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c | 2 +
drivers/gpu/drm/i915/gt/intel_context_sseu.c | 2 +
drivers/gpu/drm/i915/gt/intel_context_types.h | 2 +
drivers/gpu/drm/i915/gt/intel_lrc.c | 79 ++++++++++++++++++++++-
drivers/gpu/drm/i915/i915_drv.h | 5 ++
drivers/gpu/drm/i915/i915_sysfs.c | 32 +++++++++
drivers/gpu/drm/i915/intel_device_info.c | 59 ++++++++++++++++-
9 files changed, 218 insertions(+), 4 deletions(-)
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
