public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: Ricard Bejarano <ricard@bejarano.io>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	netdev@vger.kernel.org, michael.jamet@intel.com,
	YehezkelShB@gmail.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com
Subject: Re: Poor thunderbolt-net interface performance when bridged
Date: Wed, 3 Sep 2025 10:43:53 +0300	[thread overview]
Message-ID: <aLfxueDGLngEb7Rw@shredder> (raw)
In-Reply-To: <A68375CA-57E1-4F53-877D-480231F07942@bejarano.io>

On Tue, Sep 02, 2025 at 12:18:59PM +0200, Ricard Bejarano wrote:
> I'm afraid we don't just see it with TCP or with bridged traffic.

I wrote that it can happen with forwarded traffic, not necessarily
bridged traffic. Section 6 from here [1] shows that you get 900+ Mb/s
between blue and purple with UDP, whereas with TCP you only get around
5Mb/s.

> That was my original observation and so the title of the thread, but
> it happens at a much lower level, at the data link layer. We observed
> CRC checksum failures in link stats. You can see those in my May 27th
> message in the thread.

Assuming you are talking about [2], it shows 16763 errors out of 6360635
received packets. That's 0.2%.

> The last thing we tried was to force linearization of SKBs with fragments, to
> see if the problem is with how the driver puts those on the line, which might
> offset everything out of its place, making CRC checksums fail. I was not able
> to do it, however, as that would simply hang all my tests.
> 
> Any ideas?

I suggest removing the custom patches and re-testing with TSO disabled
(on both red and blue). If this doesn't help, you can try recording
packet drops on blue like I suggested in the previous mail.

[1] https://lore.kernel.org/netdev/29E840A2-D4DB-4A49-88FE-F97303952638@bejarano.io/
[2] https://lore.kernel.org/netdev/8672A9A1-6B32-4F81-8DFA-4122A057C9BE@bejarano.io/

  reply	other threads:[~2025-09-03  7:43 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22 17:19 Poor thunderbolt-net interface performance when bridged Ricard Bejarano
2025-05-23 11:07 ` Mika Westerberg
2025-05-23 15:07   ` Ricard Bejarano
2025-05-26  4:50     ` Mika Westerberg
2025-05-26  8:50       ` Ricard Bejarano
2025-05-26  9:22         ` Mika Westerberg
2025-05-26 11:47           ` Ricard Bejarano
2025-05-26 12:04             ` Mika Westerberg
2025-05-26 16:10               ` Ricard Bejarano
2025-05-27 10:33                 ` Mika Westerberg
2025-05-27 12:36                   ` Ricard Bejarano
2025-05-26 14:28             ` Andrew Lunn
2025-05-26 15:09               ` Stephen Hemminger
2025-05-26 19:36                 ` Ricard Bejarano
2025-05-26 19:34               ` Ricard Bejarano
2025-05-26 20:19                 ` Andrew Lunn
2025-05-27  8:47                   ` Ricard Bejarano
2025-05-27 12:51                     ` Andrew Lunn
2025-05-27 14:25                       ` Ricard Bejarano
2025-05-27 15:02                         ` Andrew Lunn
2025-05-27 18:57                           ` Ricard Bejarano
2025-05-27 19:08                             ` Andrew Lunn
2025-05-27 19:17                               ` Ricard Bejarano
2025-05-27 19:32                               ` Ricard Bejarano
2025-05-28  6:38                                 ` Ricard Bejarano
2025-05-28 11:57                                   ` Andrew Lunn
2025-05-28 13:08                                     ` Ricard Bejarano
2025-05-29 12:45                                       ` Ricard Bejarano
2025-06-14  9:13                                         ` Ricard Bejarano
2025-06-14 14:11                                           ` Andrew Lunn
2025-06-15 13:56                                             ` Ricard Bejarano
2025-06-21 11:00                                             ` Ricard Bejarano
2025-06-30  7:28                                               ` Ricard Bejarano
2025-08-28  7:59                                                 ` Ricard Bejarano
2025-09-01 20:20                                                   ` Ido Schimmel
2025-09-02 10:18                                                     ` Ricard Bejarano
2025-09-03  7:43                                                       ` Ido Schimmel [this message]
2025-09-04  8:56                                                         ` Ricard Bejarano
2025-09-04 10:33                                                           ` Ido Schimmel
2025-05-29  8:38                                     ` Ricard Bejarano
2025-05-29 10:06                                     ` Ricard Bejarano

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=aLfxueDGLngEb7Rw@shredder \
    --to=idosch@idosch.org \
    --cc=YehezkelShB@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=ricard@bejarano.io \
    /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