From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97494] Tonga vce perf regression since drm/amdgpu: add vce bypass mode for tonga.
Date: Fri, 26 Aug 2016 12:05:35 +0000 [thread overview]
Message-ID: <bug-97494-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97494
Bug ID: 97494
Summary: Tonga vce perf regression since drm/amdgpu: add vce
bypass mode for tonga.
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: adf.lists@gmail.com
R9285 agd5f drm-next-4.9-wip since
commit c04399f19436616875879ee2711c5b78a90dd1b0
Author: Rex Zhu <Rex.Zhu@amd.com>
Date: Thu Aug 18 18:27:14 2016 +0800
drm/amdgpu: add vce bypass mode for tonga.
fix issue that encode test failed on the second time when
vce dpm enabled on tonga.
vce clocks seem stuck low, forcing gpu perf to high doesn't help.
500 frames 2160p nv12 from/to ram.
omx 8 seconds -> 35
vaapi 12 seconds -> 51
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2431 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-08-26 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 12:05 bugzilla-daemon [this message]
2016-09-15 9:18 ` [Bug 97494] Tonga vce perf regression since drm/amdgpu: add vce bypass mode for tonga bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-97494-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.