From: "Timur Kristóf" <timur.kristof@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>
Cc: "michael.jamet@intel.com" <michael.jamet@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Why is Thunderbolt 3 limited to 2.5 GT/s on Linux?
Date: Wed, 03 Jul 2019 13:04:21 +0200 [thread overview]
Message-ID: <4ee5439cb01e355436d618f5d6f2e109410dc35e.camel@gmail.com> (raw)
In-Reply-To: <d1dfe289-8501-8848-6324-c43d6e66a77f@daenzer.net>
> > Okay, so I booted my system with amdgpu.benchmark=3
> > You can find the full dmesg log here: https://pastebin.com/zN9FYGw4
> >
> > The result is between 1-5 Gbit / sec depending on the transfer size
> > (the higher the better), which corresponds to neither the 8 Gbit /
> > sec
> > that the kernel thinks it is limited to, nor the 20 Gbit / sec
> > which I
> > measured earlier with pcie_bw.
>
> 5 Gbit/s throughput could be consistent with 8 Gbit/s theoretical
> bandwidth, due to various overhead.
Okay, that's good to know.
> > Since pcie_bw only shows the maximum PCIe packet size (and not the
> > actual size), could it be that it's so inaccurate that the 20 Gbit
> > /
> > sec is a fluke?
>
> Seems likely or at least plausible.
Thanks for the confirmation. It also looks like it is the slowest with
small transfers, which I assume mesa is doing for this game.
> >
> > There may be other factors, yes. I can't offer a good explanation
> > on
> > what exactly is happening, but it's pretty clear that amdgpu can't
> > take
> > full advantage of the TB3 link, so it seemed like a good idea to
> > start
> > investigating this first.
>
> Yeah, actually it would be consistent with ~16-32 KB granularity
> transfers based on your measurements above, which is plausible. So
> making sure that the driver doesn't artificially limit the PCIe
> bandwidth might indeed help.
Can you point me to the place where amdgpu decides the PCIe link speed?
I'd like to try to tweak it a little bit to see if that helps at all.
> OTOH this also indicates a similar potential for improvement by using
> larger transfers in Mesa and/or the kernel.
Yes, that sounds like it would be worth looking into.
Out of curiosity, is there a performace decrease with small transfers
on a "normal" PCIe port too, or is this specific to TB3?
Best regards,
Tim
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-07-03 11:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 10:23 Why is Thunderbolt 3 limited to 2.5 GT/s on Linux? Timur Kristóf
2019-06-28 10:32 ` Mika Westerberg
2019-06-28 11:08 ` Timur Kristóf
2019-06-28 11:34 ` Mika Westerberg
2019-06-28 12:21 ` Timur Kristóf
2019-06-28 12:53 ` Mika Westerberg
2019-06-28 13:33 ` Timur Kristóf
2019-06-28 14:14 ` Mika Westerberg
2019-06-28 14:53 ` Timur Kristóf
2019-07-01 11:44 ` Mika Westerberg
2019-07-01 14:25 ` Timur Kristóf
2019-07-01 14:28 ` Alex Deucher
2019-07-01 14:38 ` Timur Kristóf
2019-07-01 14:46 ` Alex Deucher
2019-07-01 15:10 ` Mika Westerberg
2019-07-01 14:54 ` Michel Dänzer
2019-07-01 16:01 ` Timur Kristóf
2019-07-02 8:09 ` Michel Dänzer
2019-07-02 9:49 ` Timur Kristóf
2019-07-03 8:07 ` Michel Dänzer
2019-07-03 11:04 ` Timur Kristóf [this message]
2019-07-04 8:26 ` Michel Dänzer
2019-07-05 9:17 ` Timur Kristóf
2019-07-05 13:36 ` Alex Deucher
2019-07-18 9:11 ` Timur Kristóf
2019-07-18 13:50 ` Alex Deucher
[not found] ` <172a41d97d383a8989ebd213bb4230a2df4d636d.camel@gmail.com>
2019-07-19 14:29 ` Alex Deucher
2019-07-03 18:44 ` Marek Olšák
2019-07-05 9:27 ` Timur Kristóf
2019-07-05 15:35 ` Marek Olšák
2019-07-05 16:01 ` Timur Kristóf
[not found] ` <8f0c2d7780430d40dd1e17a82484d236eae3f981.camel@gmail.com>
2019-07-18 10:29 ` Michel Dänzer
2019-07-22 9:39 ` Timur Kristóf
2019-07-23 8:11 ` Michel Dänzer
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=4ee5439cb01e355436d618f5d6f2e109410dc35e.camel@gmail.com \
--to=timur.kristof@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=michael.jamet@intel.com \
--cc=michel@daenzer.net \
--cc=mika.westerberg@linux.intel.com \
/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