From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: ccaione@baylibre.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
khilman@baylibre.com, robh+dt@kernel.org,
ingrassia@epigenesys.com, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] arm: dts: meson: Fix IRQ trigger type for macirq
Date: Fri, 7 Dec 2018 23:06:11 +0100 [thread overview]
Message-ID: <CAFBinCBCO5ZOQPRQd4WvW9FPajqdhuTZGO0L07pMX8+6VO4aEA@mail.gmail.com> (raw)
In-Reply-To: <20181207105231.25593-3-ccaione@baylibre.com>
Hi Carlo,
On Fri, Dec 7, 2018 at 11:52 AM Carlo Caione <ccaione@baylibre.com> wrote:
>
> A long running stress test on a custom board shipping an AXG SoCs and a
> Realtek RTL8211F PHY revealed that after a few hours the connection
> speed would drop drastically, from ~1000Mbps to ~3Mbps. At the same time
> the 'macirq' (eth0) IRQ would stop being triggered at all and as
> consequence the GMAC IRQs never ACKed.
>
> After a painful investigation the problem seemed to be due to a wrong
> defined IRQ type for the GMAC IRQ that should be LEVEL_HIGH instead of
> EDGE_RISING.
>
> The change in the macirq IRQ type also solved another long standing
> issue affecting this SoC/PHY where EEE was causing the network
> connection to die after stressing it with iperf3 (even though much
> sooner). It's now possible to remove the 'eee-broken-1000t' quirk as
> well.
I tested this on my Odroid-C1. however, I must admit that I never had
issues *without* eee-broken-1000t on any of my boards
without your changes:
[root@alarm ~]# iperf3 -c 192.168.1.100
Connecting to host 192.168.1.100, port 5201
[ 5] local 192.168.1.194 port 38870 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 80.6 MBytes 675 Mbits/sec 0 2.78 MBytes
[ 5] 1.00-2.00 sec 108 MBytes 904 Mbits/sec 0 3.04 MBytes
[ 5] 2.00-3.00 sec 106 MBytes 891 Mbits/sec 0 3.04 MBytes
[ 5] 3.00-4.00 sec 105 MBytes 880 Mbits/sec 0 3.04 MBytes
[ 5] 4.00-5.00 sec 65.0 MBytes 545 Mbits/sec 0 3.04 MBytes
[ 5] 5.00-6.00 sec 92.5 MBytes 777 Mbits/sec 0 3.04 MBytes
[ 5] 6.00-7.00 sec 72.5 MBytes 608 Mbits/sec 0 3.04 MBytes
[ 5] 7.00-8.19 sec 76.2 MBytes 537 Mbits/sec 0 3.04 MBytes
[ 5] 8.19-9.00 sec 48.8 MBytes 504 Mbits/sec 0 3.04 MBytes
[ 5] 9.00-10.00 sec 87.5 MBytes 736 Mbits/sec 0 3.04 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 842 MBytes 706 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 839 MBytes 701 Mbits/sec receiver
iperf Done.
[root@alarm ~]# 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
[ 5] local 192.168.1.194 port 38874 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 21.0 MBytes 175 Mbits/sec
[ 5] 1.00-2.00 sec 20.7 MBytes 174 Mbits/sec
[ 5] 2.00-3.00 sec 22.4 MBytes 187 Mbits/sec
[ 5] 3.00-4.69 sec 25.2 MBytes 125 Mbits/sec
[ 5] 4.69-5.00 sec 7.56 MBytes 206 Mbits/sec
[ 5] 5.00-6.00 sec 23.4 MBytes 196 Mbits/sec
[ 5] 6.00-7.00 sec 14.6 MBytes 123 Mbits/sec
[ 5] 7.00-8.00 sec 23.3 MBytes 196 Mbits/sec
[ 5] 8.00-9.00 sec 27.8 MBytes 233 Mbits/sec
[ 5] 9.00-10.03 sec 24.9 MBytes 203 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-9.36 sec 212 MBytes 190 Mbits/sec 1588 sender
[ 5] 0.00-10.03 sec 211 MBytes 176 Mbits/sec receiver
iperf Done.
[root@alarm ~]#
with your changes:
[root@alarm ~]# iperf3 -c 192.168.1.100
Connecting to host 192.168.1.100, port 5201
[ 5] local 192.168.1.197 port 45020 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 74.4 MBytes 624 Mbits/sec 0 2.75 MBytes
[ 5] 1.00-2.00 sec 105 MBytes 881 Mbits/sec 0 3.03 MBytes
[ 5] 2.00-3.00 sec 106 MBytes 891 Mbits/sec 0 3.03 MBytes
[ 5] 3.00-4.00 sec 78.8 MBytes 661 Mbits/sec 0 3.03 MBytes
[ 5] 4.00-5.00 sec 73.8 MBytes 617 Mbits/sec 0 3.03 MBytes
[ 5] 5.00-6.00 sec 87.5 MBytes 735 Mbits/sec 0 3.03 MBytes
[ 5] 6.00-7.15 sec 81.2 MBytes 594 Mbits/sec 0 3.03 MBytes
[ 5] 7.15-8.00 sec 61.2 MBytes 603 Mbits/sec 0 3.03 MBytes
[ 5] 8.00-9.02 sec 76.2 MBytes 625 Mbits/sec 0 3.03 MBytes
[ 5] 9.02-10.00 sec 102 MBytes 880 Mbits/sec 0 3.03 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 847 MBytes 710 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 846 MBytes 706 Mbits/sec receiver
iperf Done.
[root@alarm ~]# 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
[ 5] local 192.168.1.197 port 45024 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 22.6 MBytes 190 Mbits/sec
[ 5] 1.00-2.00 sec 19.3 MBytes 162 Mbits/sec
[ 5] 2.00-3.00 sec 22.1 MBytes 185 Mbits/sec
[ 5] 3.00-4.00 sec 29.6 MBytes 248 Mbits/sec
[ 5] 4.00-5.00 sec 30.1 MBytes 253 Mbits/sec
[ 5] 5.00-6.00 sec 16.7 MBytes 140 Mbits/sec
[ 5] 6.00-7.00 sec 21.5 MBytes 180 Mbits/sec
[ 5] 7.00-8.00 sec 14.0 MBytes 118 Mbits/sec
[ 5] 8.00-9.04 sec 20.4 MBytes 165 Mbits/sec
[ 5] 9.04-10.00 sec 19.6 MBytes 171 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.04 sec 217 MBytes 181 Mbits/sec 1795 sender
[ 5] 0.00-10.00 sec 216 MBytes 181 Mbits/sec receiver
iperf Done.
[root@alarm ~]#
RX and TX speeds are within 10Mbit/s before and after the test, so I
would call the result "identical" (within a bit of measurement
tolerance)
I'll wait a few days and see what Emiliano finds out on his board,
then I'll send my Tested-by and Acked-by
Regards
Martin
WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: ccaione@baylibre.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
khilman@baylibre.com, robh+dt@kernel.org,
ingrassia@epigenesys.com, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] arm: dts: meson: Fix IRQ trigger type for macirq
Date: Fri, 7 Dec 2018 23:06:11 +0100 [thread overview]
Message-ID: <CAFBinCBCO5ZOQPRQd4WvW9FPajqdhuTZGO0L07pMX8+6VO4aEA@mail.gmail.com> (raw)
In-Reply-To: <20181207105231.25593-3-ccaione@baylibre.com>
Hi Carlo,
On Fri, Dec 7, 2018 at 11:52 AM Carlo Caione <ccaione@baylibre.com> wrote:
>
> A long running stress test on a custom board shipping an AXG SoCs and a
> Realtek RTL8211F PHY revealed that after a few hours the connection
> speed would drop drastically, from ~1000Mbps to ~3Mbps. At the same time
> the 'macirq' (eth0) IRQ would stop being triggered at all and as
> consequence the GMAC IRQs never ACKed.
>
> After a painful investigation the problem seemed to be due to a wrong
> defined IRQ type for the GMAC IRQ that should be LEVEL_HIGH instead of
> EDGE_RISING.
>
> The change in the macirq IRQ type also solved another long standing
> issue affecting this SoC/PHY where EEE was causing the network
> connection to die after stressing it with iperf3 (even though much
> sooner). It's now possible to remove the 'eee-broken-1000t' quirk as
> well.
I tested this on my Odroid-C1. however, I must admit that I never had
issues *without* eee-broken-1000t on any of my boards
without your changes:
[root@alarm ~]# iperf3 -c 192.168.1.100
Connecting to host 192.168.1.100, port 5201
[ 5] local 192.168.1.194 port 38870 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 80.6 MBytes 675 Mbits/sec 0 2.78 MBytes
[ 5] 1.00-2.00 sec 108 MBytes 904 Mbits/sec 0 3.04 MBytes
[ 5] 2.00-3.00 sec 106 MBytes 891 Mbits/sec 0 3.04 MBytes
[ 5] 3.00-4.00 sec 105 MBytes 880 Mbits/sec 0 3.04 MBytes
[ 5] 4.00-5.00 sec 65.0 MBytes 545 Mbits/sec 0 3.04 MBytes
[ 5] 5.00-6.00 sec 92.5 MBytes 777 Mbits/sec 0 3.04 MBytes
[ 5] 6.00-7.00 sec 72.5 MBytes 608 Mbits/sec 0 3.04 MBytes
[ 5] 7.00-8.19 sec 76.2 MBytes 537 Mbits/sec 0 3.04 MBytes
[ 5] 8.19-9.00 sec 48.8 MBytes 504 Mbits/sec 0 3.04 MBytes
[ 5] 9.00-10.00 sec 87.5 MBytes 736 Mbits/sec 0 3.04 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 842 MBytes 706 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 839 MBytes 701 Mbits/sec receiver
iperf Done.
[root@alarm ~]# 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
[ 5] local 192.168.1.194 port 38874 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 21.0 MBytes 175 Mbits/sec
[ 5] 1.00-2.00 sec 20.7 MBytes 174 Mbits/sec
[ 5] 2.00-3.00 sec 22.4 MBytes 187 Mbits/sec
[ 5] 3.00-4.69 sec 25.2 MBytes 125 Mbits/sec
[ 5] 4.69-5.00 sec 7.56 MBytes 206 Mbits/sec
[ 5] 5.00-6.00 sec 23.4 MBytes 196 Mbits/sec
[ 5] 6.00-7.00 sec 14.6 MBytes 123 Mbits/sec
[ 5] 7.00-8.00 sec 23.3 MBytes 196 Mbits/sec
[ 5] 8.00-9.00 sec 27.8 MBytes 233 Mbits/sec
[ 5] 9.00-10.03 sec 24.9 MBytes 203 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-9.36 sec 212 MBytes 190 Mbits/sec 1588 sender
[ 5] 0.00-10.03 sec 211 MBytes 176 Mbits/sec receiver
iperf Done.
[root@alarm ~]#
with your changes:
[root@alarm ~]# iperf3 -c 192.168.1.100
Connecting to host 192.168.1.100, port 5201
[ 5] local 192.168.1.197 port 45020 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 74.4 MBytes 624 Mbits/sec 0 2.75 MBytes
[ 5] 1.00-2.00 sec 105 MBytes 881 Mbits/sec 0 3.03 MBytes
[ 5] 2.00-3.00 sec 106 MBytes 891 Mbits/sec 0 3.03 MBytes
[ 5] 3.00-4.00 sec 78.8 MBytes 661 Mbits/sec 0 3.03 MBytes
[ 5] 4.00-5.00 sec 73.8 MBytes 617 Mbits/sec 0 3.03 MBytes
[ 5] 5.00-6.00 sec 87.5 MBytes 735 Mbits/sec 0 3.03 MBytes
[ 5] 6.00-7.15 sec 81.2 MBytes 594 Mbits/sec 0 3.03 MBytes
[ 5] 7.15-8.00 sec 61.2 MBytes 603 Mbits/sec 0 3.03 MBytes
[ 5] 8.00-9.02 sec 76.2 MBytes 625 Mbits/sec 0 3.03 MBytes
[ 5] 9.02-10.00 sec 102 MBytes 880 Mbits/sec 0 3.03 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 847 MBytes 710 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 846 MBytes 706 Mbits/sec receiver
iperf Done.
[root@alarm ~]# 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
[ 5] local 192.168.1.197 port 45024 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 22.6 MBytes 190 Mbits/sec
[ 5] 1.00-2.00 sec 19.3 MBytes 162 Mbits/sec
[ 5] 2.00-3.00 sec 22.1 MBytes 185 Mbits/sec
[ 5] 3.00-4.00 sec 29.6 MBytes 248 Mbits/sec
[ 5] 4.00-5.00 sec 30.1 MBytes 253 Mbits/sec
[ 5] 5.00-6.00 sec 16.7 MBytes 140 Mbits/sec
[ 5] 6.00-7.00 sec 21.5 MBytes 180 Mbits/sec
[ 5] 7.00-8.00 sec 14.0 MBytes 118 Mbits/sec
[ 5] 8.00-9.04 sec 20.4 MBytes 165 Mbits/sec
[ 5] 9.04-10.00 sec 19.6 MBytes 171 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.04 sec 217 MBytes 181 Mbits/sec 1795 sender
[ 5] 0.00-10.00 sec 216 MBytes 181 Mbits/sec receiver
iperf Done.
[root@alarm ~]#
RX and TX speeds are within 10Mbit/s before and after the test, so I
would call the result "identical" (within a bit of measurement
tolerance)
I'll wait a few days and see what Emiliano finds out on his board,
then I'll send my Tested-by and Acked-by
Regards
Martin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: ccaione@baylibre.com
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
khilman@baylibre.com, robh+dt@kernel.org,
ingrassia@epigenesys.com, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/2] arm: dts: meson: Fix IRQ trigger type for macirq
Date: Fri, 7 Dec 2018 23:06:11 +0100 [thread overview]
Message-ID: <CAFBinCBCO5ZOQPRQd4WvW9FPajqdhuTZGO0L07pMX8+6VO4aEA@mail.gmail.com> (raw)
In-Reply-To: <20181207105231.25593-3-ccaione@baylibre.com>
Hi Carlo,
On Fri, Dec 7, 2018 at 11:52 AM Carlo Caione <ccaione@baylibre.com> wrote:
>
> A long running stress test on a custom board shipping an AXG SoCs and a
> Realtek RTL8211F PHY revealed that after a few hours the connection
> speed would drop drastically, from ~1000Mbps to ~3Mbps. At the same time
> the 'macirq' (eth0) IRQ would stop being triggered at all and as
> consequence the GMAC IRQs never ACKed.
>
> After a painful investigation the problem seemed to be due to a wrong
> defined IRQ type for the GMAC IRQ that should be LEVEL_HIGH instead of
> EDGE_RISING.
>
> The change in the macirq IRQ type also solved another long standing
> issue affecting this SoC/PHY where EEE was causing the network
> connection to die after stressing it with iperf3 (even though much
> sooner). It's now possible to remove the 'eee-broken-1000t' quirk as
> well.
I tested this on my Odroid-C1. however, I must admit that I never had
issues *without* eee-broken-1000t on any of my boards
without your changes:
[root@alarm ~]# iperf3 -c 192.168.1.100
Connecting to host 192.168.1.100, port 5201
[ 5] local 192.168.1.194 port 38870 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 80.6 MBytes 675 Mbits/sec 0 2.78 MBytes
[ 5] 1.00-2.00 sec 108 MBytes 904 Mbits/sec 0 3.04 MBytes
[ 5] 2.00-3.00 sec 106 MBytes 891 Mbits/sec 0 3.04 MBytes
[ 5] 3.00-4.00 sec 105 MBytes 880 Mbits/sec 0 3.04 MBytes
[ 5] 4.00-5.00 sec 65.0 MBytes 545 Mbits/sec 0 3.04 MBytes
[ 5] 5.00-6.00 sec 92.5 MBytes 777 Mbits/sec 0 3.04 MBytes
[ 5] 6.00-7.00 sec 72.5 MBytes 608 Mbits/sec 0 3.04 MBytes
[ 5] 7.00-8.19 sec 76.2 MBytes 537 Mbits/sec 0 3.04 MBytes
[ 5] 8.19-9.00 sec 48.8 MBytes 504 Mbits/sec 0 3.04 MBytes
[ 5] 9.00-10.00 sec 87.5 MBytes 736 Mbits/sec 0 3.04 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 842 MBytes 706 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 839 MBytes 701 Mbits/sec receiver
iperf Done.
[root@alarm ~]# 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
[ 5] local 192.168.1.194 port 38874 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 21.0 MBytes 175 Mbits/sec
[ 5] 1.00-2.00 sec 20.7 MBytes 174 Mbits/sec
[ 5] 2.00-3.00 sec 22.4 MBytes 187 Mbits/sec
[ 5] 3.00-4.69 sec 25.2 MBytes 125 Mbits/sec
[ 5] 4.69-5.00 sec 7.56 MBytes 206 Mbits/sec
[ 5] 5.00-6.00 sec 23.4 MBytes 196 Mbits/sec
[ 5] 6.00-7.00 sec 14.6 MBytes 123 Mbits/sec
[ 5] 7.00-8.00 sec 23.3 MBytes 196 Mbits/sec
[ 5] 8.00-9.00 sec 27.8 MBytes 233 Mbits/sec
[ 5] 9.00-10.03 sec 24.9 MBytes 203 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-9.36 sec 212 MBytes 190 Mbits/sec 1588 sender
[ 5] 0.00-10.03 sec 211 MBytes 176 Mbits/sec receiver
iperf Done.
[root@alarm ~]#
with your changes:
[root@alarm ~]# iperf3 -c 192.168.1.100
Connecting to host 192.168.1.100, port 5201
[ 5] local 192.168.1.197 port 45020 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 74.4 MBytes 624 Mbits/sec 0 2.75 MBytes
[ 5] 1.00-2.00 sec 105 MBytes 881 Mbits/sec 0 3.03 MBytes
[ 5] 2.00-3.00 sec 106 MBytes 891 Mbits/sec 0 3.03 MBytes
[ 5] 3.00-4.00 sec 78.8 MBytes 661 Mbits/sec 0 3.03 MBytes
[ 5] 4.00-5.00 sec 73.8 MBytes 617 Mbits/sec 0 3.03 MBytes
[ 5] 5.00-6.00 sec 87.5 MBytes 735 Mbits/sec 0 3.03 MBytes
[ 5] 6.00-7.15 sec 81.2 MBytes 594 Mbits/sec 0 3.03 MBytes
[ 5] 7.15-8.00 sec 61.2 MBytes 603 Mbits/sec 0 3.03 MBytes
[ 5] 8.00-9.02 sec 76.2 MBytes 625 Mbits/sec 0 3.03 MBytes
[ 5] 9.02-10.00 sec 102 MBytes 880 Mbits/sec 0 3.03 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 847 MBytes 710 Mbits/sec 0 sender
[ 5] 0.00-10.05 sec 846 MBytes 706 Mbits/sec receiver
iperf Done.
[root@alarm ~]# 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
[ 5] local 192.168.1.197 port 45024 connected to 192.168.1.100 port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 22.6 MBytes 190 Mbits/sec
[ 5] 1.00-2.00 sec 19.3 MBytes 162 Mbits/sec
[ 5] 2.00-3.00 sec 22.1 MBytes 185 Mbits/sec
[ 5] 3.00-4.00 sec 29.6 MBytes 248 Mbits/sec
[ 5] 4.00-5.00 sec 30.1 MBytes 253 Mbits/sec
[ 5] 5.00-6.00 sec 16.7 MBytes 140 Mbits/sec
[ 5] 6.00-7.00 sec 21.5 MBytes 180 Mbits/sec
[ 5] 7.00-8.00 sec 14.0 MBytes 118 Mbits/sec
[ 5] 8.00-9.04 sec 20.4 MBytes 165 Mbits/sec
[ 5] 9.04-10.00 sec 19.6 MBytes 171 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.04 sec 217 MBytes 181 Mbits/sec 1795 sender
[ 5] 0.00-10.00 sec 216 MBytes 181 Mbits/sec receiver
iperf Done.
[root@alarm ~]#
RX and TX speeds are within 10Mbit/s before and after the test, so I
would call the result "identical" (within a bit of measurement
tolerance)
I'll wait a few days and see what Emiliano finds out on his board,
then I'll send my Tested-by and Acked-by
Regards
Martin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2018-12-07 22:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 10:52 [PATCH v2 0/2] meson: Fix IRQ trigger type Carlo Caione
2018-12-07 10:52 ` Carlo Caione
2018-12-07 10:52 ` Carlo Caione
2018-12-07 10:52 ` [PATCH v2 1/2] arm64: dts: meson: Fix IRQ trigger type for macirq Carlo Caione
2018-12-07 10:52 ` Carlo Caione
2018-12-07 10:52 ` Carlo Caione
2018-12-08 0:20 ` Kevin Hilman
2018-12-08 0:20 ` Kevin Hilman
2018-12-08 0:20 ` Kevin Hilman
2018-12-07 10:52 ` [PATCH v2 2/2] arm: " Carlo Caione
2018-12-07 10:52 ` Carlo Caione
2018-12-07 10:52 ` Carlo Caione
2018-12-07 18:51 ` Emiliano Ingrassia
2018-12-07 18:51 ` Emiliano Ingrassia
2018-12-07 18:51 ` Emiliano Ingrassia
2018-12-08 10:46 ` Carlo Caione
2018-12-08 10:46 ` Carlo Caione
2018-12-08 10:46 ` Carlo Caione
2018-12-12 10:49 ` Emiliano Ingrassia
2018-12-12 10:49 ` Emiliano Ingrassia
2018-12-12 10:49 ` Emiliano Ingrassia
2018-12-07 22:06 ` Martin Blumenstingl [this message]
2018-12-07 22:06 ` Martin Blumenstingl
2018-12-07 22:06 ` Martin Blumenstingl
2018-12-29 0:17 ` Martin Blumenstingl
2018-12-29 0:17 ` Martin Blumenstingl
2018-12-29 0:17 ` Martin Blumenstingl
2019-01-11 0:21 ` Kevin Hilman
2019-01-11 0:21 ` Kevin Hilman
2019-01-11 0:21 ` Kevin Hilman
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=CAFBinCBCO5ZOQPRQd4WvW9FPajqdhuTZGO0L07pMX8+6VO4aEA@mail.gmail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=ccaione@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=ingrassia@epigenesys.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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.