From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218525] Thunderbolt eGPU bad performance
Date: Mon, 06 Jan 2025 22:12:59 +0000 [thread overview]
Message-ID: <bug-218525-208809-5gQ5xisuau@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218525-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218525
--- Comment #18 from Kaukov (kaukov.peter@pm.me) ---
After a lot of discussion on https://github.com/doitsujin/dxvk/issues/3694, a
user suggested we try out a DXVK config option. Lo and behold, all the FPS
issues were fixed.
Turns out the issue comes from DXVK itself and isn't related to the kernel.
You can close this bug because it's not a bug with the kernel and is in no way
related to it.
Thank you for keeping it open for so long!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-01-06 22:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 10:14 [Bug 218525] New: Thunderbolt eGPU bad performance bugzilla-daemon
2024-02-24 11:45 ` [Bug 218525] " bugzilla-daemon
2024-02-26 6:35 ` bugzilla-daemon
2024-02-29 1:49 ` bugzilla-daemon
2024-02-29 1:50 ` bugzilla-daemon
2024-02-29 1:50 ` bugzilla-daemon
2024-02-29 1:55 ` bugzilla-daemon
2024-02-29 1:55 ` bugzilla-daemon
2024-02-29 9:07 ` bugzilla-daemon
2024-03-01 6:42 ` bugzilla-daemon
2024-03-01 8:59 ` bugzilla-daemon
2024-03-01 9:00 ` bugzilla-daemon
2024-03-01 9:00 ` bugzilla-daemon
2024-03-01 9:39 ` bugzilla-daemon
2024-03-01 9:46 ` bugzilla-daemon
2024-03-06 2:18 ` bugzilla-daemon
2024-03-08 8:17 ` bugzilla-daemon
2024-09-08 12:53 ` bugzilla-daemon
2025-01-06 22:12 ` bugzilla-daemon [this message]
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-218525-208809-5gQ5xisuau@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).