[Bug 102199] Kabylake has poor performance, doesn't upclock during activity quickly with single display configurations

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=102199

--- Comment #15 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to Ray Strode [halfline] from comment #14)
> wouldn't the boosting need to happen before the drawing was started, not
> after its drawn and before its swapped ?

With the glFinish, the boost would be applied to the rendering. It's just that
you end up with a synchronous step prior to SwapBuffers.

> can the driver just boost whenever an input device fires off an event ? keep
> interactive performance up when the user is interacting...

How to determine which request corresponds to the interactive stream? As a gfx
driver we have no knowledge of input devices. The system as a whole struggles
to identify interactive processes! The easiest way for us to identify user
tasks is by looking at what affects the output. We could look for special
objects (i.e. framebuffers) in the command stream and use that as a flag, but
really we have to balance perf/power and waitboosting is a policy that I would
much rather punt to userspace. (For me having a flag on a context that says all
work submitted via that context is interactive seems a sensible compromise.)

My ideal interface for submitting tasks would include a deadline; almost as a
rule user tasks have a clear deadline and opencl/transcode does not. But we are
at very early stages of a GPU scheduler, a long way off SCHED_DEADLINE.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170818/bf1ba0a5/attachment.html>