From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99974] Pinned memory is extremely slow on Dolphin
Date: Sun, 26 Feb 2017 17:00:20 +0000 [thread overview]
Message-ID: <bug-99974-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1222 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99974
Bug ID: 99974
Summary: Pinned memory is extremely slow on Dolphin
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: akz@tutanota.com
QA Contact: dri-devel@lists.freedesktop.org
When running Dolphin with the OpenGL backend and pinned memory enabled, I get
terrible performance. Getting about 10-20fps in a 60fps game with pinned
memory, and full 60fps without it.
This was discussed on dolphin's IRC channel earlier today, and this PR was made
to disable it. If it gets committed you'll have to use a build without that
code to test it I think.
https://github.com/dolphin-emu/dolphin/pull/4973/commits/005e6796b85341a3e79fc93e49337bb8d4e67fdf
I'm using an RX460, Linux 4.10.0, mesa/llvm/xorg-server all built from git,
although it happens on older stable versions too.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2701 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:[~2017-02-26 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 17:00 bugzilla-daemon [this message]
2017-03-07 21:20 ` [Bug 99974] Pinned memory is extremely slow on Dolphin bugzilla-daemon
2019-09-25 17:57 ` 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-99974-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.