<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - KDE Konsole very slow scrolling with TearFree and QT graphics system native"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77436#c141">Comment # 141</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - KDE Konsole very slow scrolling with TearFree and QT graphics system native"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77436">bug 77436</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>I've restored the throttling and tried to compromise to not over-throttle
during allocations:
commit ca0d06add926eb17fcec6c031adabb656498d744
Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Date: Wed Jun 25 14:19:33 2014 +0100
sna: Improve throttling during bo allocation
By controlling how long we may block during buffer allocation, we can
relax the throttle elsewhere to prevent render lag buildup.
References: <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO --- - KDE Konsole very slow scrolling with TearFree and QT graphics system native"
href="show_bug.cgi?id=77436">https://bugs.freedesktop.org/show_bug.cgi?id=77436</a>
Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
Can you please check that prevents the lag buildup on both TearFree and
non-TearFree setups?
Due to the well flips are scheduled in TearFree there can easily be a 20ms
delay between render and seeing the results, at best 16ms. That should be
enough to make non-TearFree feel snappier. To improve, I would need to submit
the next frame just before the vblank to minimise the render output latency.
The current solution is nice for its simplicity. :)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>