From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218525] Thunderbolt eGPU bad performance
Date: Mon, 26 Feb 2024 06:35:09 +0000 [thread overview]
Message-ID: <bug-218525-208809-HDvsF7KJyx@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 #2 from Mika Westerberg (mika.westerberg@linux.intel.com) ---
I'm not a graphics expert but I wonder if you have tried to run some benchmark
that works the same on both Windows and Linux? I understand that most of the
games you play in Linux are using some sort of "emulation" and that might have
some affect here (which is then issue that you need to take with the folks who
develop that part if it turns out to be the problem).
I did some testing back then with Unigine Heaven:
https://benchmark.unigine.com/heaven
Can you perhaps run that (or anything similar) and see what's the difference
between the two OSSes on that same hardware?
Then we would need to understand the hardware configuration, can you add the
full dmesg and output of 'sudo lspci -vv' when you have the eGPU plugged in?
The third thing that comes to mind is that do you have any PCIe ASPM states
enabled? That can be seen in the dmesg too I think and also in the lspci dump.
Also do you have the monitor connected directly to the eGPU outputs or the
host?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-02-26 6:35 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 [this message]
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
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-HDvsF7KJyx@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).