From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218525] Thunderbolt eGPU bad performance
Date: Fri, 01 Mar 2024 06:42:10 +0000 [thread overview]
Message-ID: <bug-218525-208809-zB2VVaxyjh@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 #9 from Mika Westerberg (mika.westerberg@linux.intel.com) ---
Okay I see a couple of things from HW side that may affect (or may not). First
is that the real PCIe link to the 06:00 eGPU device is running on limited
bandwidth:
LnkSta: Speed 5GT/s (downgraded), Width x4 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
I don't know why this is but it could be that the graphics driver tunes this
because it finds the virtual links only supporting gen 1 speeds. However, this
is not true, the virtual PCIe links over Thunderbolt can get up to 90% of the
40G link if there is no other tunneling (such as DisplayPort).
The second thing is that there is ASPM L1 enabled on this same real PCIe link:
LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
I suggest trying to disable it. Passing something like
"pcie_aspm.policy=performance" should make the above to turn into ASPM disabled
or so.
Also I suggest experimenting to disable IOMMU (pass intel_iommu=off in the
kernel command line).
--
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-03-01 6:42 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 [this message]
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-zB2VVaxyjh@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 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.