From: Jerome Brunet <jbrunet@baylibre•com>
To: "André Roth" <neolynx@gmail•com>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail•com>,
Johnson Leung <r58129@freescale•com>,
Giuseppe CAVALLARO <peppe.cavallaro@st•com>,
linux-amlogic@lists•infradead.org,
Alexandre Torgue <alexandre.torgue@st•com>,
netdev@vger•kernel.org
Subject: Re: stmmac/RTL8211F/Meson GXBB: TX throughput problems
Date: Mon, 14 Nov 2016 11:49:34 +0100 [thread overview]
Message-ID: <1479120574.29252.29.camel@baylibre.com> (raw)
In-Reply-To: <20161113201339.667ac1f7@gmail.com>
On Sun, 2016-11-13 at 20:13 +0100, André Roth wrote:
> >
> > Andre, the 3.14 kernel you are talking, is it this one ? :
> > https://github.com/hardkernel/linux/tree/odroidc2-3.14.y
>
> yes
>
> >
> > Because in drivers/net/phy/realtek.c, they disable EEE, but
> > also 1000Base-T Full Duplex advertisement ?
> >
> > + /* disable 1000m adv*/
> > + val = phy_read(phydev, 0x9);
> > + phy_write(phydev, 0x9, val&(~(1<<9)));
> >
> > If this is the kernel you are running, you should not be able to
> > have
> > ethernet at 1000MB/s ? Or is it in half duplex mode ?
>
> ethtool shows 1000Mb/s Full-Duplex and the bandwith is around 300Mb/s
> (as measured by scp). kernel version: 3.14.65-73
Andre,
I checked again the kernel at https://github.com/hardkernel/linux/tree/
odroidc2-3.14.y. The version you mention (3.14.65-73) seems to be:
sha1: c75d5f4d1516cdd86d90a9d1c565bb0ed9251036
tag: jenkins-deb s905 kernel-73
In this particular version, both realtek drivers:
- drivers/net/phy/realtek.c
- drivers/amlogic/ethernet/phy/am_realtek.c
have the hack to disable 1000M advertisement. I don't understand how it
possible for you to have 1000Base-T Full Duplex with this, maybe I'm
missing something here ?
If you did compile the kernel yourself, could you check the 2 file
mentioned above ? Just to be sure there was no patch applied at the
last minute, which would not show up in the git history of hardkernel ?
Thx
Jerome
>
>
next prev parent reply other threads:[~2016-11-14 10:49 UTC|newest]
Thread overview: 28+ 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-12 16:37 ` Alexandre Torgue
2016-09-12 21:26 ` Martin Blumenstingl
2016-09-17 21:23 ` André Roth
2016-09-26 6:17 ` Giuseppe CAVALLARO
2016-10-01 15:58 ` Martin Blumenstingl
2016-11-03 16:36 ` Jerome Brunet
2016-11-05 12:20 ` Martin Blumenstingl
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-14 15:30 ` Giuseppe CAVALLARO
2016-09-18 20:42 ` André Roth
2016-09-19 5:38 ` Giuseppe CAVALLARO
2016-10-01 20:15 ` Martin Blumenstingl
2016-10-01 20:40 ` Martin Blumenstingl
2016-10-31 10:25 ` André Roth
2016-11-03 16:57 ` Jerome Brunet
2016-11-07 10:59 ` Giuseppe CAVALLARO
2016-11-07 17:37 ` Martin Blumenstingl
2016-11-14 7:47 ` Giuseppe CAVALLARO
2016-11-14 11:02 ` Jerome Brunet
2016-11-14 15:00 ` Andreas Färber
2016-11-15 11:27 ` Jerome Brunet
2016-11-13 19:13 ` André Roth
2016-11-14 10:49 ` Jerome Brunet [this message]
2016-11-17 18:44 ` André Roth
2016-11-17 21:47 ` Jerome Brunet
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=1479120574.29252.29.camel@baylibre.com \
--to=jbrunet@baylibre$(echo .)com \
--cc=alexandre.torgue@st$(echo .)com \
--cc=linux-amlogic@lists$(echo .)infradead.org \
--cc=martin.blumenstingl@googlemail$(echo .)com \
--cc=neolynx@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peppe.cavallaro@st$(echo .)com \
--cc=r58129@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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