From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 97075] VCE encoding slow when GPU is not stressed (HD 7970M)
Date: Mon, 25 Jul 2016 14:43:53 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0632478792=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id DD7836E383
for ; Mon, 25 Jul 2016 14:43:52 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0632478792==
Content-Type: multipart/alternative; boundary="14694578321.6A245aD.12421";
charset="UTF-8"
--14694578321.6A245aD.12421
Date: Mon, 25 Jul 2016 14:43:52 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D97075
Christian K=C3=B6nig changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
Priority|medium |high
--- Comment #1 from Christian K=C3=B6nig ---
Yeah, that is a known issue.
The current VA-API implementation waits for the result after sending a sing=
le
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.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--14694578321.6A245aD.12421
Date: Mon, 25 Jul 2016 14:43:52 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Christian K=C3=B6nig
changed
bug 97075<=
/a>
| What |
Removed |
Added |
| Severity |
normal
|
enhancement
|
| Priority |
medium
|
high
|
Comment=
# 1
on bug 97075<=
/a>
from Christian K=C3=B6nig
Yeah, that is a known issue.
The current VA-API implementation waits for the result after sending a sing=
le
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.
You are receiving this mail because:
- You are the assignee for the bug.
=
--14694578321.6A245aD.12421--
--===============0632478792==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0632478792==--