From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198511] lags in youtube videos 1080p 60fps with radeon hd4650 and kernel 4.15rc8
Date: Mon, 22 Jan 2018 03:01:53 +0000 [thread overview]
Message-ID: <bug-198511-2300-OXHh8ljcU9@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198511-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #28 from Barto (mister.freeman@laposte.net) ---
I made another test, by using a player like VLC and a video file ( 1080p, 60
FPS ) :
- with a video file 1080p@60 fps, GPU acceleration disabled ( XV output ) and
kernel 4.15rc8 : I can notice a slight degradation, but less visible than
firefox, it needs a trained eye in order to notice the performance issue,
- with a video file 1080p@60 fps, GPU acceleration enabled ( VDPAU ) and kernel
4.15rc8 : all is ok, perfect 60 FPS frame, 100% smooth playback
- with a video file 1080p@60 fps, GPU acceleration disabled ( XV output ) and
kernel 4.14.14: all is ok
the key here is the video resolution and framerate, things get difficult for my
CPU when we reach the resolution 1080p AND the framerate 60 fps, any weak/non
optimized algorithm in kernel ( or video driver ) will likely trigger slight
lags/frame drops,
if I use the "cheat mode" ( GPU acceleration with VDPAU ) then all is ok, no
lags when the video has a resolution 1080p/60 fps and when I use kernel
4.15rc8.
It would be interesting to create a benchmark ( a simple source code in C ) in
order to evaluate with precision ( with a number ) the performance level of
your algorithm related to drm/ttm, it will make easy the comparison between
kernel 4.14.14 ( old algorithm ) and kernel 4.15rc8
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-22 3:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 19:54 [Bug 198511] New: lags in youtube videos 1080p 60fps with radeon hd4650 and kernel 4.15rc8 bugzilla-daemon
2018-01-18 19:56 ` [Bug 198511] " bugzilla-daemon
2018-01-18 19:57 ` bugzilla-daemon
2018-01-18 20:35 ` bugzilla-daemon
2018-01-18 20:58 ` bugzilla-daemon
2018-01-19 21:17 ` bugzilla-daemon
2018-01-19 21:18 ` bugzilla-daemon
2018-01-19 21:20 ` bugzilla-daemon
2018-01-19 22:09 ` bugzilla-daemon
2018-01-19 22:10 ` bugzilla-daemon
2018-01-20 1:26 ` bugzilla-daemon
2018-01-20 1:29 ` bugzilla-daemon
2018-01-20 4:11 ` bugzilla-daemon
2018-01-20 15:59 ` bugzilla-daemon
2018-01-20 17:33 ` bugzilla-daemon
2018-01-21 8:07 ` bugzilla-daemon
2018-01-21 9:50 ` bugzilla-daemon
2018-01-21 10:14 ` bugzilla-daemon
2018-01-21 15:06 ` bugzilla-daemon
2018-01-21 15:19 ` bugzilla-daemon
2018-01-21 15:50 ` bugzilla-daemon
2018-01-21 16:08 ` bugzilla-daemon
2018-01-21 16:35 ` bugzilla-daemon
2018-01-21 17:20 ` bugzilla-daemon
2018-01-21 17:48 ` bugzilla-daemon
2018-01-21 18:07 ` bugzilla-daemon
2018-01-21 19:17 ` bugzilla-daemon
2018-01-21 19:38 ` bugzilla-daemon
2018-01-22 3:01 ` bugzilla-daemon [this message]
2018-01-22 8:44 ` bugzilla-daemon
2018-02-10 23:28 ` 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-198511-2300-OXHh8ljcU9@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.