linux-amlogic.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Simon Huelck <simonmail@gmx.de>
To: 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 16:02:35 +0100	[thread overview]
Message-ID: <8382d8d8-c015-be59-c712-00eec5b40c70@gmx.de> (raw)
In-Reply-To: <8ec64936-c8fa-1f0e-68bf-2ad1d6e8f5d9@gmx.de>

Am 24.02.2019 um 16:00 schrieb Simon Huelck:
> Am 21.02.2019 um 18:46 schrieb Jerome Brunet:
>> On Thu, 2019-02-21 at 18:27 +0100, Simon Huelck wrote:
>>> Hi,
>>>
>>>
>>>
>>> this was changed recently, with a patch for the EEE stuff , see here:
>>>
>>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.0-rc7&id=e35e26b26e955c53e61c154ba26b9bb15da6b858
>> Hu, I was not aware this finally went through. Good !
>> As explained in the patch and by Jose, the GMAC should be using IRQ_LEVEL.
>>
>> The realtek PHY has EEE enabled by default. Having this enabled generates a
>> lot of (Low Power) Interrupts.
>>
>> Previously, when the GMAC used IRQ_EDGE. Because it is wrong, we would
>> eventually miss an IRQ and the interface would just die. Unfortunately, it was
>> not that easy find out.
>>
>> 2 years ago, we just noticed that disabling EEE would make the failure go
>> away. Forcing this EEE feature off through DT was merely a work around.
>>
>> Now that the real cause of the problem is known, there is no reason to keep
>> this hack around.
>>
>> Whether EEE adds a performance penality and why, is another topic.
>> As Jose pointed out, you can disable EEE at runtime, using ethtool.
>>
>> Jerome
>>
> Hi,
>
>
> i tested the latest patches of **next-20190222, there were some stmmac
> improvements.**
>
> **
> **
>
> **For the topic i got , the performance stayed identical.**
>
> **C:\Users\Simon\Downloads\iperf3.6_64bit\iperf3.6_64bit>iperf3.exe -c
> 10.10.11.1 -i1
> warning: Ignoring nonsense TCP MSS 0
> Connecting to host 10.10.11.1, port 5201
> [  5] local 10.10.11.100 port 50830 connected to 10.10.11.1 port 5201
> [ ID] Interval           Transfer     Bitrate
> [  5]   0.00-1.00   sec  78.9 MBytes   661 Mbits/sec
> [  5]   1.00-2.00   sec  79.1 MBytes   664 Mbits/sec
> [  5]   2.00-3.00   sec  79.4 MBytes   666 Mbits/sec
> [  5]   3.00-4.00   sec  34.4 MBytes   288 Mbits/sec
> [  5]   4.00-5.00   sec  16.1 MBytes   135 Mbits/sec
> [  5]   5.00-6.00   sec  15.8 MBytes   132 Mbits/sec
> [  5]   6.00-7.00   sec  14.2 MBytes   120 Mbits/sec
> [  5]   7.00-8.00   sec  15.6 MBytes   131 Mbits/sec
> [  5]   8.00-9.00   sec  14.9 MBytes   125 Mbits/sec
> [  5]   9.00-10.00  sec  15.0 MBytes   126 Mbits/sec
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval           Transfer     Bitrate
> [  5]   0.00-10.00  sec   363 MBytes   305 Mbits/sec                  sender
> [  5]   0.00-10.04  sec   363 MBytes   303 Mbits/sec                 
> receiver
>
> **
>
> **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
> **
>
> **
> **
>
Hi,


and another thing that i recognized , TX from my odroid stays around 450
Mbits ( is not affected by RX). but RX suffers alot from the TX stuff (
the max sum of RX/TX seems to be the magical 650MBits)


regards,

Simon


_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

  reply	other threads:[~2019-02-24 15:05 UTC|newest]

Thread overview: 48+ 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-02-04 14:34     ` Martin Blumenstingl
2019-02-06 10:36       ` Emiliano Ingrassia
2019-02-06 18:04         ` Simon Huelck
2019-02-06 21:21         ` Simon Huelck
2019-02-07 19:30         ` Simon Huelck
2019-02-09  1:09           ` Martin Blumenstingl
2019-02-11 13:44             ` Jose Abreu
2019-02-14  7:21               ` Simon Huelck
2019-02-17 14:48               ` Martin Blumenstingl
2019-02-17 19:13                 ` Simon Huelck
2019-02-18  8:42                 ` Jose Abreu
2019-02-18  8:45                   ` Jose Abreu
2019-02-18 12:33                     ` Simon Huelck
2019-02-18 12:41                       ` Jose Abreu
2019-02-18 13:02                         ` Jose Abreu
2019-02-18 15:29                           ` Simon Huelck
2019-02-18 15:31                             ` Jose Abreu
2019-02-18 15:53                               ` Simon Huelck
2019-02-18 16:26                                 ` Jose Abreu
2019-02-18 16:40                                   ` Simon Huelck
2019-02-18 16:43                                     ` Jose Abreu
2019-02-18 16:51                                       ` Simon Huelck
2019-02-18 17:05                                         ` Jose Abreu
2019-02-18 18:05                                           ` Simon Huelck
2019-02-19  8:47                                             ` Jose Abreu
2019-02-19 19:41                                               ` Simon Huelck
2019-02-21 14:21                                                 ` Jerome Brunet
2019-02-21 17:27                                                   ` Simon Huelck
2019-02-21 17:46                                                     ` Jerome Brunet
2019-02-21 19:34                                                       ` Simon Huelck
2019-02-22 17:21                                                         ` Anand Moon
2019-02-24 15:00                                                       ` Simon Huelck
2019-02-24 15:02                                                         ` Simon Huelck [this message]
2019-02-24 19:42                                                         ` Sebastian Gottschall
2019-02-24 20:34                                                           ` Simon Huelck
2019-02-27 11:09                                                             ` Jose Abreu
2019-02-27 19:02                                                               ` Simon Huelck
2019-03-01  9:23                                                                 ` Jose Abreu
2019-03-05  9:55                                                                   ` Simon Huelck
2019-03-06 11:35                                                                     ` Simon Huelck
2019-03-06 11:45                                                                       ` Simon Huelck
2019-05-11 14:53                                                                   ` Simon Huelck
2019-05-13  9:07                                                                     ` Jose Abreu
2019-05-22 12:48                                                                       ` Simon Huelck
2019-05-22 14:02                                                                       ` Neil Armstrong
2019-02-27 21:03                                                               ` 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=8382d8d8-c015-be59-c712-00eec5b40c70@gmx.de \
    --to=simonmail@gmx.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 \
    /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;
as well as URLs for NNTP newsgroup(s).