All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: stmmac/RTL8211F/Meson GXBB: TX throughput problems
Date: Tue, 15 Nov 2016 12:27:56 +0100	[thread overview]
Message-ID: <1479209276.2619.10.camel@baylibre.com> (raw)
In-Reply-To: <24b4d9b3-0a9d-5f6c-7dc2-5fcbb1012481@suse.de>

On Mon, 2016-11-14 at 16:00 +0100, Andreas F?rber wrote:
> Hi,
> 
> Am 07.11.2016 um 18:37 schrieb Martin Blumenstingl:
> > 
> > The same problem still appears on my Tronsmart Vega S95 Meta even
> > with
> > the patched PHY driver.
> > 
> > Unfortunately I don't have a second device to rule out that my
> > Tronsmart Vega S95 Meta could be broken (not unlikely, I get DDR
> > errors from time to time in u-boot). Maybe Andreas Faerber can test
> > ethernet with and without Jerome's patch on one of his Tronsmart
> > devices.
> 
> So far I only ran into the stall issue on my Odroid-C2, not on my
> Vega
> S95 Telos, both on v4.10/integ branch with a rebased MMC patch of
> yours
> on top.

The status of vega/mxq boards seems a bit confused.
This is the status I have so far:
These designs are not affected by the EEE issue. The patch mentioned
has no effect on these boards.
Some boards run fine at GBit speed (like yours) , some have terrible Tx
throughput (like mine and Martin's one). However, unlike on the
odroidc2, the link is not broken after the test, it is not necessary to
ifdown/ifup the interface to do another test.

I'm wondering if the vega/mxq designs all use the rtl8211f phy ?

> 
> I'm assuming you mean realtek8211f-disable-eee-1000.patch from Nov 3.
> 

Indeed. I won't submit anything for the vega since it has no effect.

> Regards,
> Andreas
> 

WARNING: multiple messages have this Message-ID (diff)
From: Jerome Brunet <jbrunet@baylibre.com>
To: "Andreas Färber" <afaerber@suse.de>,
	"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>
Cc: "Giuseppe CAVALLARO" <peppe.cavallaro@st.com>,
	"Alexandre Torgue" <alexandre.torgue@st.com>,
	netdev@vger.kernel.org, "André Roth" <neolynx@gmail.com>,
	"Johnson Leung" <r58129@freescale.com>,
	linux-amlogic@lists.infradead.org
Subject: Re: stmmac/RTL8211F/Meson GXBB: TX throughput problems
Date: Tue, 15 Nov 2016 12:27:56 +0100	[thread overview]
Message-ID: <1479209276.2619.10.camel@baylibre.com> (raw)
In-Reply-To: <24b4d9b3-0a9d-5f6c-7dc2-5fcbb1012481@suse.de>

On Mon, 2016-11-14 at 16:00 +0100, Andreas Färber wrote:
> Hi,
> 
> Am 07.11.2016 um 18:37 schrieb Martin Blumenstingl:
> > 
> > The same problem still appears on my Tronsmart Vega S95 Meta even
> > with
> > the patched PHY driver.
> > 
> > Unfortunately I don't have a second device to rule out that my
> > Tronsmart Vega S95 Meta could be broken (not unlikely, I get DDR
> > errors from time to time in u-boot). Maybe Andreas Faerber can test
> > ethernet with and without Jerome's patch on one of his Tronsmart
> > devices.
> 
> So far I only ran into the stall issue on my Odroid-C2, not on my
> Vega
> S95 Telos, both on v4.10/integ branch with a rebased MMC patch of
> yours
> on top.

The status of vega/mxq boards seems a bit confused.
This is the status I have so far:
These designs are not affected by the EEE issue. The patch mentioned
has no effect on these boards.
Some boards run fine at GBit speed (like yours) , some have terrible Tx
throughput (like mine and Martin's one). However, unlike on the
odroidc2, the link is not broken after the test, it is not necessary to
ifdown/ifup the interface to do another test.

I'm wondering if the vega/mxq designs all use the rtl8211f phy ?

> 
> I'm assuming you mean realtek8211f-disable-eee-1000.patch from Nov 3.
> 

Indeed. I won't submit anything for the vega since it has no effect.

> Regards,
> Andreas
> 

  reply	other threads:[~2016-11-15 11:27 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-11 20:39 stmmac/RTL8211F/Meson GXBB: TX throughput problems Martin Blumenstingl
2016-09-11 20:39 ` Martin Blumenstingl
2016-09-12 16:37 ` Alexandre Torgue
2016-09-12 16:37   ` Alexandre Torgue
2016-09-12 21:26   ` Martin Blumenstingl
2016-09-12 21:26     ` Martin Blumenstingl
2016-09-17 21:23     ` André Roth
2016-09-17 21:23       ` André Roth
2016-09-26  6:17       ` Giuseppe CAVALLARO
2016-09-26  6:17         ` Giuseppe CAVALLARO
2016-10-01 15:58         ` Martin Blumenstingl
2016-10-01 15:58           ` Martin Blumenstingl
2016-11-03 16:36           ` Jerome Brunet
2016-11-03 16:36             ` Jerome Brunet
2016-11-05 12:20             ` Martin Blumenstingl
2016-11-05 12:20               ` Martin Blumenstingl
2016-11-13 19:20             ` André Roth
2016-11-13 19:20               ` André Roth
     [not found] ` <216F2694-1C1D-44DA-AC15-57ED15C24BBE@bluematt.me>
2016-09-12 21:29   ` Martin Blumenstingl
2016-09-12 21:29     ` Martin Blumenstingl
2016-09-14 15:30 ` Giuseppe CAVALLARO
2016-09-14 15:30   ` Giuseppe CAVALLARO
2016-09-18 20:42   ` André Roth
2016-09-18 20:42     ` André Roth
2016-09-19  5:38     ` Giuseppe CAVALLARO
2016-09-19  5:38       ` Giuseppe CAVALLARO
2016-10-01 20:15   ` Martin Blumenstingl
2016-10-01 20:15     ` Martin Blumenstingl
2016-10-01 20:40     ` Martin Blumenstingl
2016-10-01 20:40       ` Martin Blumenstingl
2016-10-31 10:25     ` André Roth
2016-10-31 10:25       ` André Roth
2016-11-03 16:57       ` Jerome Brunet
2016-11-03 16:57         ` Jerome Brunet
2016-11-07 10:59         ` Giuseppe CAVALLARO
2016-11-07 10:59           ` Giuseppe CAVALLARO
2016-11-07 17:37           ` Martin Blumenstingl
2016-11-07 17:37             ` Martin Blumenstingl
2016-11-14  7:47             ` Giuseppe CAVALLARO
2016-11-14  7:47               ` Giuseppe CAVALLARO
2016-11-14 11:02               ` Jerome Brunet
2016-11-14 11:02                 ` Jerome Brunet
2016-11-14 15:00             ` Andreas Färber
2016-11-14 15:00               ` Andreas Färber
2016-11-15 11:27               ` Jerome Brunet [this message]
2016-11-15 11:27                 ` Jerome Brunet
2016-11-13 19:13         ` André Roth
2016-11-13 19:13           ` André Roth
2016-11-14 10:49           ` Jerome Brunet
2016-11-14 10:49             ` Jerome Brunet
2016-11-17 18:44             ` André Roth
2016-11-17 18:44               ` André Roth
2016-11-17 21:47               ` Jerome Brunet
2016-11-17 21:47                 ` Jerome Brunet
2016-10-01 20:26   ` Martin Blumenstingl
2016-10-01 20:26     ` Martin Blumenstingl

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=1479209276.2619.10.camel@baylibre.com \
    --to=jbrunet@baylibre.com \
    --cc=linus-amlogic@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 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.