<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> <span class="fn">Christian König</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - VCE encoding slow when GPU is not stressed (HD 7970M)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97075">bug 97075</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;">Severity</td>
<td>normal
</td>
<td>enhancement
</td>
</tr>
<tr>
<td style="text-align:right;">Priority</td>
<td>medium
</td>
<td>high
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - VCE encoding slow when GPU is not stressed (HD 7970M)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97075#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - VCE encoding slow when GPU is not stressed (HD 7970M)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97075">bug 97075</a>
from <span class="vcard"><a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> <span class="fn">Christian König</span></a>
</span></b>
<pre>Yeah, that is a known issue.
The current VA-API implementation waits for the result after sending a single
frame to the hardware.
The OpenMAX implementation pipelines the whole thing and waits for a result
after sending multiple frames to the hardware to chew on.
So with OpenMAX the hardware is always busy, while with VA-API it constantly
turns on/off.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>