<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - [BXT] up to 6% performance drop with "i965: Set "Subslice Hashing Mode" to 16x16 on Apollolake""
href="https://bugs.freedesktop.org/show_bug.cgi?id=102272">bug 102272</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - [BXT] up to 6% performance drop with "i965: Set "Subslice Hashing Mode" to 16x16 on Apollolake""
href="https://bugs.freedesktop.org/show_bug.cgi?id=102272#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - [BXT] up to 6% performance drop with "i965: Set "Subslice Hashing Mode" to 16x16 on Apollolake""
href="https://bugs.freedesktop.org/show_bug.cgi?id=102272">bug 102272</a>
from <span class="vcard"><a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> <span class="fn">Eero Tamminen</span></a>
</span></b>
<pre>Bisect verified that the memory bandwidth improvements on 18 EU BXT:
- 5% GLB 2.7 Fill, SynMark ZBuffer, GpuTest Triangle (fullscreen)
- 3% SynMark TexMem* & TexFilterTri
were also from the same Hashing Mode change that caused the perf drops.
When investigating the Fill case with performance counters, 16x16 hashing mode
improves the cache hit rate as expected, which explains the performance
improvement.
-> Marking as wontfix, the perf regressions from the commit are acceptable
compromise compared to improvements.
If there are important use-cases with huge amounts of really small triangles
where 16x16 can regress performance, it may make sense to have this as DRI conf
option for the context creation.
(If terrain tessellation perf dropping, but geom instancing not with 16x16 mode
is because of their different triangle ordering, that raises a question why
tessellation in GPU side produces triangle order that's aligned worse for the
16x16 hashing mode.)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>