From: Erik Beck <xunil@tahomasoft.com>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, heiko@sntech.de,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH 3/4] arm64: dts: rockchip: Add HINLINK H68K
Date: Mon, 1 Sep 2025 06:24:37 -0400 [thread overview]
Message-ID: <20250901062437.780cc71a.xunil@tahomasoft.com> (raw)
In-Reply-To: <20250901070008.68662-1-amadeus@jmu.edu.cn>
On Mon, 1 Sep 2025 15:00:08 +0800
Chukun Pan <amadeus@jmu.edu.cn> wrote:
> Hi,
>
> > Please change phy-mode here to "rgmii". This change will yield an
> > ethernet speed throughput change of a factor of 100+.
>
> > Same as above: Please change phy-mode here to "rgmii". This change
> > will yield an ethernet speed throughput change of a factor of 100+.
>
> This doesn't make sense. When I first submitted it to coolsnowwolf/lede
> in 2022, I used "rgmii-id" as the phy-mode, and it worked:
> https://github.com/coolsnowwolf/lede/blob/master/target/linux/rockchip/files/arch/arm64/boot/dts/rockchip/rk3568-opc-h68k.dts#L24
>
> Are you experiencing issues with both eth0 and eth1 or just one of them?
> Are you using the generic-rk3568 target for U-Boot?
>
Hi Chukun, thanks for your response.
At Andrew Lunn's suggestion, I'm doing
more granular and rigorous testing, now using iperf3. I'll post more details
of results here after I retest a couple of scenarios.
However, I will report now that so far, I'm getting better (faster) and more
consistent results using iperf3.
~Erik
> I can't reproduce your problem in my test.
>
> eth0/gmac1 (as lan):
> root@OpenWrt:~# iperf3 -c 192.168.1.100
> Connecting to host 192.168.1.100, port 5201
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-10.00 sec 1.10 GBytes 942 Mbits/sec 29 sender
> [ 5] 0.00-10.04 sec 1.10 GBytes 936 Mbits/sec
> receiver
>
> root@OpenWrt:~# iperf3 -c 192.168.1.100 -R
> Connecting to host 192.168.1.100, port 5201
> Reverse mode, remote host 192.168.1.100 is sending
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-10.04 sec 1.10 GBytes 939 Mbits/sec 1 sender
> [ 5] 0.00-10.00 sec 1.10 GBytes 941 Mbits/sec
> receiver
>
> eth1/gmac0 (as wan):
> root@OpenWrt:~# iperf3 -c 192.168.0.2 -P 4
> Connecting to host 192.168.0.2, port 5201
> [ ID] Interval Transfer Bitrate Retr
> [SUM] 0.00-10.00 sec 1.10 GBytes 945 Mbits/sec 1191
> sender [SUM] 0.00-10.05 sec 1.09 GBytes 935 Mbits/sec
> receiver
>
> root@OpenWrt:~# iperf3 -c 192.168.0.2 -R
> Connecting to host 192.168.0.2, port 5201
> Reverse mode, remote host 192.168.0.2 is sending
> [ ID] Interval Transfer Bitrate Retr
> [ 5] 0.00-10.06 sec 1.10 GBytes 939 Mbits/sec 6 sender
> [ 5] 0.00-10.00 sec 1.10 GBytes 941 Mbits/sec
> receiver
>
> --
> 2.25.1
>
>
>
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-09-01 10:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 10:00 [PATCH 0/4] arm64: dts: rockchip: Add HINLINK H66K/H68K Chukun Pan
2025-08-18 10:00 ` [PATCH 1/4] dt-bindings: vendor-prefixes: Add HINLINK Chukun Pan
2025-08-18 10:00 ` [PATCH 2/4] dt-bindings: arm: rockchip: Add HINLINK H66K / H68K Chukun Pan
2025-08-18 10:00 ` [PATCH 3/4] arm64: dts: rockchip: Add HINLINK H68K Chukun Pan
2025-08-30 21:14 ` Erik Beck
2025-08-30 21:30 ` Andrew Lunn
2025-08-30 22:21 ` Erik Beck
2025-08-31 14:48 ` Erik Beck
2025-08-31 15:53 ` Andrew Lunn
2025-08-31 16:28 ` Erik Beck
2025-09-01 0:47 ` Andrew Lunn
2025-09-01 7:00 ` Chukun Pan
2025-09-01 10:24 ` Erik Beck [this message]
2025-09-01 14:06 ` Erik Beck
2025-09-02 7:00 ` Chukun Pan
2025-09-02 12:10 ` Erik Beck
2025-09-01 16:25 ` Erik Beck
2025-08-18 10:00 ` [PATCH 4/4] arm64: dts: rockchip: Add HINLINK H66K Chukun Pan
2025-08-18 17:27 ` [PATCH 0/4] arm64: dts: rockchip: Add HINLINK H66K/H68K Conor Dooley
2025-08-24 10:54 ` Heiko Stuebner
2025-08-30 21:11 ` Erik Beck
2025-08-30 21:26 ` Andrew Lunn
2025-08-30 22:20 ` Erik Beck
2025-08-31 13:55 ` Erik Beck
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=20250901062437.780cc71a.xunil@tahomasoft.com \
--to=xunil@tahomasoft.com \
--cc=amadeus@jmu.edu.cn \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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
all inboxes | Powered by JetHome®