From: Andrew Lunn <andrew@lunn.ch>
To: Yachen Liu <blankwonder@gmail.com>
Cc: netdev@vger.kernel.org, michael.jamet@intel.com,
mika.westerberg@linux.intel.com, YehezkelShB@gmail.com
Subject: Re: [Bug][USB4NET] Potential Bug with USB4NET and Linux Bridging
Date: Fri, 15 Sep 2023 14:53:46 +0200 [thread overview]
Message-ID: <5d2f7260-819f-4197-b3a6-a7146cb71f66@lunn.ch> (raw)
In-Reply-To: <CAPsLH6aHJGG7kAaZ7hdyKoSor4Ws2Fwujjjxog6E_bQrY1fA+w@mail.gmail.com>
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.
Maybe three is a concept mix up here. TSO is TCP Segmentation Offload.
The network stack gives the NIC a large buffer and a template
Ethernet, IP and TCP header. The NIC is then supposed to send MTU
sized frames on the wire, performing segmentation and appending real
headers to each Frame.
We also have Jumbo packets. These are a single frames which are bigger
than he standard 1500 MTU.
You can also combine these. So the stack could for example pass a 64K
buffer to the NIC for TSO, and the MTU could be 8K. So you would
expect to see 8 frames on the wire.
When running tcpdump, what do you actually see? Is TSO actually
happening? Are the frames the size of the MTU or less?
Andrew
prev parent reply other threads:[~2023-09-15 12:53 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
2023-09-14 16:07 ` Yachen Liu
2023-09-15 12:53 ` Andrew Lunn [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=5d2f7260-819f-4197-b3a6-a7146cb71f66@lunn.ch \
--to=andrew@lunn.ch \
--cc=YehezkelShB@gmail.com \
--cc=blankwonder@gmail.com \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.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.