<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - 3% perf drop in GfxBench Manhattan 3.0, 3.1 and CarChase test-cases" href="https://bugs.freedesktop.org/show_bug.cgi?id=111090#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - 3% perf drop in GfxBench Manhattan 3.0, 3.1 and CarChase test-cases" href="https://bugs.freedesktop.org/show_bug.cgi?id=111090">bug 111090</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>Note that commit 8ee36e048c98d4015804a23f884be2576f778a93 Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Date: Thu Jun 20 15:20:52 2019 +0100 drm/i915/execlists: Minimalistic timeslicing If we have multiple contexts of equal priority pending execution, activate a timer to demote the currently executing context in favour of the next in the queue when that timeslice expires. This enforces fairness between contexts (so long as they allow preemption -- forced preemption, in the future, will kick those who do not obey) and allows us to avoid userspace blocking forward progress with e.g. unbounded MI_SEMAPHORE_WAIT. is at least one intentional change in the scheduling that may interfere with throughput tests (like gfxbench) in the presence of third parties (X) also trying to render. Except that is nowhere need the mentioned commits -- so I will have to check, but if you could keep an eye out for any potential regression from that (such need to be minimised and find some justification).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>