<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - 5-10% drop in Lightsmark2008 from "i965/miptree: Store fast clear colors in an isl_color_value""
href="https://bugs.freedesktop.org/show_bug.cgi?id=101678#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - 5-10% drop in Lightsmark2008 from "i965/miptree: Store fast clear colors in an isl_color_value""
href="https://bugs.freedesktop.org/show_bug.cgi?id=101678">bug 101678</a>
from <span class="vcard"><a class="email" href="mailto:jason@jlekstrand.net" title="Jason Ekstrand <jason@jlekstrand.net>"> <span class="fn">Jason Ekstrand</span></a>
</span></b>
<pre>I'm not surprised that the "fix" bisects to that patch. It should fix the same
underlying performance issue (the added resolves) but for completely different
reasons. The patch I sent over the weekend reverses the change from May and
fixes the issue that way. I think my new patch is still needed as it will
matter in the multi-slice case (it mattered in all cases back in may). I'd
like to verify that my patch on top of the "bad" commit in May restores the
original performance.</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>