public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Georg Gottleuber <ggo@tuxedocomputers.com>
Cc: Yao Zi <me@ziyao.cc>,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, Frank.Sae@motor-comm.com,
	hkallweit1@gmail.com, vladimir.oltean@nxp.com, wens@csie.org,
	jszhang@kernel.org, 0x1207@gmail.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	jeffbai@aosc.io, kexybiscuit@aosc.io
Subject: Re: [PATCH RESEND net-next v6 0/3] Add DWMAC glue driver for Motorcomm YT6801
Date: Mon, 19 Jan 2026 15:43:44 +0000	[thread overview]
Message-ID: <aW5RMKqwpYTZ9uFH@shell.armlinux.org.uk> (raw)
In-Reply-To: <147b700c-cae2-4286-b532-ec408e00b004@tuxedocomputers.com>

On Mon, Jan 19, 2026 at 04:33:17PM +0100, Georg Gottleuber wrote:
> Hi,
> 
> I tested this driver with our TUXEDO InfinityBook Pro AMD Gen9. Iperf
> revealed that tx is only 100Mbit/s:
> 
> ## YT6801 TX
> 
> [ ID] Interval           Transfer     Bitrate         Retr  Cwnd
> [  5]   0.00-1.00   sec  8.75 MBytes  73.3 Mbits/sec    0    164 KBytes
> 
> [  5]   1.00-2.00   sec  8.62 MBytes  72.4 Mbits/sec    0    164 KBytes
> 
> [  5]   2.00-3.00   sec  8.62 MBytes  72.4 Mbits/sec    0    164 KBytes
> 
> [  5]   3.00-4.00   sec  8.12 MBytes  68.2 Mbits/sec    0    164 KBytes
> 
> [  5]   4.00-5.00   sec  8.62 MBytes  72.3 Mbits/sec    0    164 KBytes
> 
> [  5]   5.00-6.00   sec  8.50 MBytes  71.3 Mbits/sec    0    164 KBytes
> 
> [  5]   6.00-7.00   sec  8.25 MBytes  69.2 Mbits/sec    0    164 KBytes
> 
> [  5]   7.00-8.00   sec  8.62 MBytes  72.4 Mbits/sec    0    164 KBytes
> 
> [  5]   8.00-9.00   sec  8.50 MBytes  71.3 Mbits/sec    0    164 KBytes
> 
> [  5]   9.00-10.00  sec  8.62 MBytes  72.3 Mbits/sec    0    164 KBytes
> 
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval           Transfer     Bitrate         Retr
> [  5]   0.00-10.00  sec  85.2 MBytes  71.5 Mbits/sec    0             sender
> [  5]   0.00-10.05  sec  84.4 MBytes  70.5 Mbits/sec
> receiver
> 
> 
> ## YT6801 RX
> 
> [ ID] Interval           Transfer     Bitrate
> [  5]   0.00-1.00   sec   112 MBytes   939 Mbits/sec
> [  5]   1.00-2.00   sec   112 MBytes   941 Mbits/sec
> [  5]   2.00-3.00   sec   112 MBytes   941 Mbits/sec
> [  5]   3.00-4.00   sec   112 MBytes   942 Mbits/sec
> [  5]   4.00-5.00   sec   112 MBytes   942 Mbits/sec
> [  5]   5.00-6.00   sec   112 MBytes   943 Mbits/sec
> [  5]   6.00-7.00   sec   112 MBytes   941 Mbits/sec
> [  5]   7.00-8.00   sec   112 MBytes   942 Mbits/sec
> [  5]   8.00-9.00   sec   112 MBytes   942 Mbits/sec
> [  5]   9.00-10.00  sec   112 MBytes   941 Mbits/sec
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval           Transfer     Bitrate         Retr
> [  5]   0.00-10.04  sec  1.10 GBytes   941 Mbits/sec   88             sender
> [  5]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec
> receiver
> 
> With our normally used DKMS module, Ethernet works with full-duplex and
> gigabit. Attached are some logs from lspci and dmesg. Do you have any
> idea how I can debug this further?

My suggestion would be:

- Look at the statistics, e.g.

   ip -s li sh dev enp2s0

- apply
  https://lore.kernel.org/r/E1vgtBc-00000005D6v-040n@rmk-PC.armlinux.org.uk
  to enable more statistics to work, and check the network driver
  statistics:

   ethtool --statistics enp2s0

to see if there's any clues for what is going on.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2026-01-19 15:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  9:34 [PATCH RESEND net-next v6 0/3] Add DWMAC glue driver for Motorcomm YT6801 Yao Zi
2026-01-09  9:34 ` [PATCH RESEND net-next v6 1/3] net: phy: motorcomm: Support YT8531S PHY in YT6801 Ethernet controller Yao Zi
2026-01-09 10:06   ` Russell King (Oracle)
2026-01-09  9:34 ` [PATCH RESEND net-next v6 2/3] net: stmmac: Add glue driver for Motorcomm YT6801 ethernet controller Yao Zi
2026-01-12  6:10   ` Sai Krishna Gajula
2026-01-12  7:51     ` Yao Zi
2026-01-12 10:17     ` Russell King (Oracle)
2026-01-09  9:34 ` [PATCH RESEND net-next v6 3/3] MAINTAINERS: Assign myself as maintainer of Motorcomm DWMAC glue driver Yao Zi
2026-01-13  3:30 ` [PATCH RESEND net-next v6 0/3] Add DWMAC glue driver for Motorcomm YT6801 patchwork-bot+netdevbpf
2026-01-19 15:33   ` Georg Gottleuber
2026-01-19 15:43     ` Russell King (Oracle) [this message]
2026-01-19 17:45       ` Georg Gottleuber
2026-01-19 17:57         ` Georg Gottleuber
2026-01-20  2:45           ` Yao Zi
2026-01-20  9:42             ` Georg Gottleuber
2026-01-20 11:52               ` Yao Zi
2026-01-21  7:10                 ` Xi Ruoyao

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=aW5RMKqwpYTZ9uFH@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=0x1207@gmail.com \
    --cc=Frank.Sae@motor-comm.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ggo@tuxedocomputers.com \
    --cc=hkallweit1@gmail.com \
    --cc=jeffbai@aosc.io \
    --cc=jszhang@kernel.org \
    --cc=kexybiscuit@aosc.io \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@ziyao.cc \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox