From: Sebastian Gottschall <s.gottschall@newmedia-net.de> To: Simon Huelck <simonmail@gmx.de>, Jerome Brunet <jbrunet@baylibre.com>, Jose Abreu <jose.abreu@synopsys.com>, Martin Blumenstingl <martin.blumenstingl@googlemail.com> Cc: linux-amlogic@lists.infradead.org, Gpeppe.cavallaro@st.com, alexandre.torgue@st.com, Emiliano Ingrassia <ingrassia@epigenesys.com>, netdev@vger.kernel.org Subject: Re: stmmac / meson8b-dwmac Date: Sun, 24 Feb 2019 20:42:58 +0100 [thread overview] Message-ID: <f08f2659-dde0-41ec-9233-6b4d5f375ffe@newmedia-net.de> (raw) In-Reply-To: <8ec64936-c8fa-1f0e-68bf-2ad1d6e8f5d9@gmx.de> > ** > > **its clearly visible when i activated the other stream for getting > duplex load ... The highest rate also stays alot under the possible > 930MBits that i have seen earlier with 4.14. > ** > > ** > ** > > **the parallel stream reached around 450Mbits , which almost sums up to > 660Mbits. This is what i meant when i said that duplex might be broken. > ** > > ** > ** > > **Connecting to host 10.10.11.100, port 5201 > [ 5] local 10.10.11.1 port 38658 connected to 10.10.11.100 port 5201 > [ ID] Interval Transfer Bitrate Retr Cwnd > [ 5] 0.00-1.00 sec 62.9 MBytes 528 Mbits/sec 0 65.6 KBytes > [ 5] 1.00-2.00 sec 56.9 MBytes 477 Mbits/sec 0 65.6 KBytes > [ 5] 2.00-3.00 sec 55.9 MBytes 469 Mbits/sec 0 65.6 KBytes > [ 5] 3.00-4.00 sec 53.0 MBytes 445 Mbits/sec 0 65.6 KBytes > [ 5] 4.00-5.00 sec 54.3 MBytes 455 Mbits/sec 0 65.6 KBytes > [ 5] 5.00-6.00 sec 54.8 MBytes 460 Mbits/sec 0 65.6 KBytes > [ 5] 6.00-7.00 sec 45.3 MBytes 380 Mbits/sec 0 65.6 KBytes > [ 5] 7.00-8.00 sec 51.2 MBytes 429 Mbits/sec 0 65.6 KBytes > [ 5] 8.00-9.00 sec 56.1 MBytes 470 Mbits/sec 0 65.6 KBytes > [ 5] 9.00-10.00 sec 55.3 MBytes 464 Mbits/sec 0 65.6 KBytes > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.00 sec 546 MBytes 458 Mbits/sec 0 sender > [ 5] 0.00-10.00 sec 545 MBytes 457 Mbits/sec > receiver** > > ** > ** > > **regards,** > > **Simon > ** > > ** > ** which stmac device are you talking about? its not your windows pc. if its a ipq8064 based device or something like that you should look on a very different location. this platform like the r7800 has stmac performance problems since the kernel clk code for this device is lets say "very wrong". so alot of clocks arent correct and so the ethernet performance will suffer. i can tell you that i'm able to get 930 mbit on a stmmac based device. but as i said. the kernel needs other numerous fixes to get a good performance root@TEW827:~# iperf3 -c 10.88.193.134 -i 1 Connecting to host 10.88.193.134, port 5201 [ 5] local 10.88.193.90 port 36024 connected to 10.88.193.134 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 108 MBytes 903 Mbits/sec 0 5.17 MBytes [ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 5.17 MBytes [ 5] 2.00-3.00 sec 109 MBytes 913 Mbits/sec 0 6.02 MBytes [ 5] 3.00-4.00 sec 112 MBytes 944 Mbits/sec 0 6.02 MBytes [ 5] 4.00-5.00 sec 109 MBytes 910 Mbits/sec 1 6.02 MBytes [ 5] 5.00-6.00 sec 111 MBytes 935 Mbits/sec 0 6.02 MBytes [ 5] 6.00-7.00 sec 109 MBytes 912 Mbits/sec 1 6.02 MBytes ^C[ 5] 7.00-7.51 sec 56.2 MBytes 935 Mbits/sec 0 6.02 MBytes > >
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Gottschall <s.gottschall@newmedia-net.de> To: Simon Huelck <simonmail@gmx.de>, Jerome Brunet <jbrunet@baylibre.com>, Jose Abreu <jose.abreu@synopsys.com>, Martin Blumenstingl <martin.blumenstingl@googlemail.com> Cc: linux-amlogic@lists.infradead.org, netdev@vger.kernel.org, alexandre.torgue@st.com, Emiliano Ingrassia <ingrassia@epigenesys.com>, Gpeppe.cavallaro@st.com Subject: Re: stmmac / meson8b-dwmac Date: Sun, 24 Feb 2019 20:42:58 +0100 [thread overview] Message-ID: <f08f2659-dde0-41ec-9233-6b4d5f375ffe@newmedia-net.de> (raw) In-Reply-To: <8ec64936-c8fa-1f0e-68bf-2ad1d6e8f5d9@gmx.de> > ** > > **its clearly visible when i activated the other stream for getting > duplex load ... The highest rate also stays alot under the possible > 930MBits that i have seen earlier with 4.14. > ** > > ** > ** > > **the parallel stream reached around 450Mbits , which almost sums up to > 660Mbits. This is what i meant when i said that duplex might be broken. > ** > > ** > ** > > **Connecting to host 10.10.11.100, port 5201 > [ 5] local 10.10.11.1 port 38658 connected to 10.10.11.100 port 5201 > [ ID] Interval Transfer Bitrate Retr Cwnd > [ 5] 0.00-1.00 sec 62.9 MBytes 528 Mbits/sec 0 65.6 KBytes > [ 5] 1.00-2.00 sec 56.9 MBytes 477 Mbits/sec 0 65.6 KBytes > [ 5] 2.00-3.00 sec 55.9 MBytes 469 Mbits/sec 0 65.6 KBytes > [ 5] 3.00-4.00 sec 53.0 MBytes 445 Mbits/sec 0 65.6 KBytes > [ 5] 4.00-5.00 sec 54.3 MBytes 455 Mbits/sec 0 65.6 KBytes > [ 5] 5.00-6.00 sec 54.8 MBytes 460 Mbits/sec 0 65.6 KBytes > [ 5] 6.00-7.00 sec 45.3 MBytes 380 Mbits/sec 0 65.6 KBytes > [ 5] 7.00-8.00 sec 51.2 MBytes 429 Mbits/sec 0 65.6 KBytes > [ 5] 8.00-9.00 sec 56.1 MBytes 470 Mbits/sec 0 65.6 KBytes > [ 5] 9.00-10.00 sec 55.3 MBytes 464 Mbits/sec 0 65.6 KBytes > - - - - - - - - - - - - - - - - - - - - - - - - - > [ ID] Interval Transfer Bitrate Retr > [ 5] 0.00-10.00 sec 546 MBytes 458 Mbits/sec 0 sender > [ 5] 0.00-10.00 sec 545 MBytes 457 Mbits/sec > receiver** > > ** > ** > > **regards,** > > **Simon > ** > > ** > ** which stmac device are you talking about? its not your windows pc. if its a ipq8064 based device or something like that you should look on a very different location. this platform like the r7800 has stmac performance problems since the kernel clk code for this device is lets say "very wrong". so alot of clocks arent correct and so the ethernet performance will suffer. i can tell you that i'm able to get 930 mbit on a stmmac based device. but as i said. the kernel needs other numerous fixes to get a good performance root@TEW827:~# iperf3 -c 10.88.193.134 -i 1 Connecting to host 10.88.193.134, port 5201 [ 5] local 10.88.193.90 port 36024 connected to 10.88.193.134 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 108 MBytes 903 Mbits/sec 0 5.17 MBytes [ 5] 1.00-2.00 sec 112 MBytes 943 Mbits/sec 0 5.17 MBytes [ 5] 2.00-3.00 sec 109 MBytes 913 Mbits/sec 0 6.02 MBytes [ 5] 3.00-4.00 sec 112 MBytes 944 Mbits/sec 0 6.02 MBytes [ 5] 4.00-5.00 sec 109 MBytes 910 Mbits/sec 1 6.02 MBytes [ 5] 5.00-6.00 sec 111 MBytes 935 Mbits/sec 0 6.02 MBytes [ 5] 6.00-7.00 sec 109 MBytes 912 Mbits/sec 1 6.02 MBytes ^C[ 5] 7.00-7.51 sec 56.2 MBytes 935 Mbits/sec 0 6.02 MBytes > > _______________________________________________ linux-amlogic mailing list linux-amlogic@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2019-02-24 20:00 UTC|newest] Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <a38e643c-ed9f-c306-cc95-84f70ebc1f10@gmx.de> [not found] ` <CAFBinCDebPOsmrhSXecx48nGWHh7g_OGPbr1Y0M+n_v9Ht91ew@mail.gmail.com> 2019-01-17 21:23 ` stmmac / meson8b-dwmac Simon Huelck 2019-01-17 21:23 ` Simon Huelck 2019-02-04 14:34 ` Martin Blumenstingl 2019-02-04 14:34 ` Martin Blumenstingl 2019-02-06 10:36 ` Emiliano Ingrassia 2019-02-06 10:36 ` Emiliano Ingrassia 2019-02-06 18:04 ` Simon Huelck 2019-02-06 18:04 ` Simon Huelck 2019-02-06 21:21 ` Simon Huelck 2019-02-06 21:21 ` Simon Huelck 2019-02-07 19:30 ` Simon Huelck 2019-02-07 19:30 ` Simon Huelck 2019-02-09 1:09 ` Martin Blumenstingl 2019-02-09 1:09 ` Martin Blumenstingl 2019-02-11 13:44 ` Jose Abreu 2019-02-11 13:44 ` Jose Abreu 2019-02-14 7:21 ` Simon Huelck 2019-02-14 7:21 ` Simon Huelck 2019-02-17 14:48 ` Martin Blumenstingl 2019-02-17 14:48 ` Martin Blumenstingl 2019-02-17 19:13 ` Simon Huelck 2019-02-17 19:13 ` Simon Huelck 2019-02-18 8:42 ` Jose Abreu 2019-02-18 8:42 ` Jose Abreu 2019-02-18 8:45 ` Jose Abreu 2019-02-18 8:45 ` Jose Abreu 2019-02-18 12:33 ` Simon Huelck 2019-02-18 12:33 ` Simon Huelck 2019-02-18 12:41 ` Jose Abreu 2019-02-18 12:41 ` Jose Abreu 2019-02-18 13:02 ` Jose Abreu 2019-02-18 13:02 ` Jose Abreu 2019-02-18 15:29 ` Simon Huelck 2019-02-18 15:29 ` Simon Huelck 2019-02-18 15:31 ` Jose Abreu 2019-02-18 15:31 ` Jose Abreu 2019-02-18 15:53 ` Simon Huelck 2019-02-18 15:53 ` Simon Huelck 2019-02-18 16:26 ` Jose Abreu 2019-02-18 16:26 ` Jose Abreu 2019-02-18 16:40 ` Simon Huelck 2019-02-18 16:40 ` Simon Huelck 2019-02-18 16:43 ` Jose Abreu 2019-02-18 16:43 ` Jose Abreu 2019-02-18 16:51 ` Simon Huelck 2019-02-18 16:51 ` Simon Huelck 2019-02-18 17:05 ` Jose Abreu 2019-02-18 17:05 ` Jose Abreu 2019-02-18 18:05 ` Simon Huelck 2019-02-18 18:05 ` Simon Huelck 2019-02-19 8:47 ` Jose Abreu 2019-02-19 8:47 ` Jose Abreu 2019-02-19 19:41 ` Simon Huelck 2019-02-19 19:41 ` Simon Huelck 2019-02-21 14:21 ` Jerome Brunet 2019-02-21 14:21 ` Jerome Brunet 2019-02-21 17:27 ` Simon Huelck 2019-02-21 17:27 ` Simon Huelck 2019-02-21 17:46 ` Jerome Brunet 2019-02-21 17:46 ` Jerome Brunet 2019-02-21 19:34 ` Simon Huelck 2019-02-21 19:34 ` Simon Huelck 2019-02-22 17:21 ` Anand Moon 2019-02-22 17:21 ` Anand Moon 2019-02-24 15:00 ` Simon Huelck 2019-02-24 15:00 ` Simon Huelck 2019-02-24 15:02 ` Simon Huelck 2019-02-24 15:02 ` Simon Huelck 2019-02-24 19:42 ` Sebastian Gottschall [this message] 2019-02-24 19:42 ` Sebastian Gottschall 2019-02-24 20:34 ` Simon Huelck 2019-02-24 20:34 ` Simon Huelck 2019-02-27 11:09 ` Jose Abreu 2019-02-27 11:09 ` Jose Abreu 2019-02-27 19:02 ` Simon Huelck 2019-02-27 19:02 ` Simon Huelck 2019-03-01 9:23 ` Jose Abreu 2019-03-01 9:23 ` Jose Abreu 2019-03-05 9:55 ` Simon Huelck 2019-03-05 9:55 ` Simon Huelck 2019-03-06 11:35 ` Simon Huelck 2019-03-06 11:35 ` Simon Huelck 2019-03-06 11:45 ` Simon Huelck 2019-03-06 11:45 ` Simon Huelck 2019-05-11 14:53 ` Simon Huelck 2019-05-11 14:53 ` Simon Huelck 2019-05-13 9:07 ` Jose Abreu 2019-05-13 9:07 ` Jose Abreu 2019-05-22 12:48 ` Simon Huelck 2019-05-22 12:48 ` Simon Huelck 2019-05-22 14:02 ` Neil Armstrong 2019-05-22 14:02 ` Neil Armstrong 2019-02-27 21:03 ` Simon Huelck 2019-02-27 21:03 ` Simon Huelck 2019-02-18 17:05 ` Simon Huelck 2019-02-18 17:05 ` Simon Huelck
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=f08f2659-dde0-41ec-9233-6b4d5f375ffe@newmedia-net.de \ --to=s.gottschall@newmedia-net.de \ --cc=Gpeppe.cavallaro@st.com \ --cc=alexandre.torgue@st.com \ --cc=ingrassia@epigenesys.com \ --cc=jbrunet@baylibre.com \ --cc=jose.abreu@synopsys.com \ --cc=linux-amlogic@lists.infradead.org \ --cc=martin.blumenstingl@googlemail.com \ --cc=netdev@vger.kernel.org \ --cc=simonmail@gmx.de \ /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: linkBe 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.