From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Yachen Liu <blankwonder@gmail.com>
Cc: netdev@vger.kernel.org, michael.jamet@intel.com, YehezkelShB@gmail.com
Subject: Re: [Bug][USB4NET] Potential Bug with USB4NET and Linux Bridging
Date: Thu, 14 Sep 2023 18:51:26 +0300 [thread overview]
Message-ID: <20230914155126.GM1599918@black.fi.intel.com> (raw)
In-Reply-To: <CAPsLH6aHJGG7kAaZ7hdyKoSor4Ws2Fwujjjxog6E_bQrY1fA+w@mail.gmail.com>
Hi,
On Thu, Sep 14, 2023 at 10:02:24PM +0800, Yachen Liu wrote:
> Hello,
>
> I've noticed a potential issue with USB4NET when used in conjunction
> with Linux bridging. I'm uncertain if it's a bug or a configuration
> oversight on my part.
>
> In essence, when the device at the other end of Thunderbolt sends
> packets using the TSO mechanism (default behavior in macOS), the Linux
> thunderbolt0 interface correctly receives this large packet. However,
> the packet isn't properly forwarded to another device via bridging.
>
> Detailed Description:
>
> The test environment consists of three systems:
>
> A: Mac Mini (M2): macOS Sonoma 14.0 RC
> B: Proxmox VE 8.0. Kernel release: 6.2.16-3-pve, acting as the Host system.
> C: Debian. A Guest system running within B.
>
> System A and B are connected via USB4, while System C is a virtual
> machine within B. On B, thunderbolt0 and tap102i0 are bridged to
> establish a connection between A and C.
>
> During an iperf3 speed test between A and B, I've achieved
> bi-directional speeds of around 18Gbps. Between B and C, the speeds
> are 100Gbps+ at their peak, with a minimum of 28Gbps.
>
> However, when performing an iperf3 speed test between A and C, the
> direction from C to A shows about 18Gbps, but from A to C, the speed
> drops to just tens of Kbps, essentially making it unusable.
>
> If tested using UDP, both directions achieve roughly 5Gbps. (I suspect
> some buffer issue in macOS limiting the speed).
>
> After various tests and investigations, I found that by setting
> macOS's net.inet.tcp.tso to 0 (disabling TSO), speeds from A to C
> improved to around 10Gbps.
>
> Packet capture via tcpdump revealed that macOS writes large packets
> (over 10000B) to Thunderbolt Networking using TSO. These packets are
> correctly captured on thunderbolt0, but are missing from tap102i0,
> resulting in significant packet loss.
>
> Since ethtool doesn't support the thunderbolt0 device, further testing
> has been hindered.
>
> I'm unsure if this is a bug, or if it could be resolved via
> configuration. If more information is needed, I am more than willing
> to assist further with tests.
Thank you for the report. To be honest, I'm not sure how the interface
should in this case and is there perhaps some way for a NIC driver to
pass TSO packets up so that they would be passed in the same way to the
tap interface. Is there any example driver where this works? Like if you
use ethernet instead of TBT/USB4 does that work with TSO packets?
next prev parent reply other threads:[~2023-09-14 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 14:02 [Bug][USB4NET] Potential Bug with USB4NET and Linux Bridging Yachen Liu
2023-09-14 15:51 ` Mika Westerberg [this message]
2023-09-14 16:07 ` Yachen Liu
2023-09-15 12:53 ` Andrew Lunn
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=20230914155126.GM1599918@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=blankwonder@gmail.com \
--cc=michael.jamet@intel.com \
--cc=netdev@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.