From: "Leonidas P. Papadakos" <papadakospan@gmail.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Jose Abreu" <jose.abreu@synopsys.com>,
"Alexandre Torgue" <alexandre.torgue@st.com>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Christoph Müllner" <christoph.muellner@theobroma-systems.com>,
"Klaus Goger" <klaus.goger@theobroma-systems.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Heiko Stübner" <heiko@sntech.de>
Subject: Re: [PATCH 1/2] stmmac: introduce flag to dynamically disable TX offload for rockchip devices
Date: Fri, 05 Apr 2019 21:38:57 +0300 [thread overview]
Message-ID: <1554489537.1199.0@gmail.com> (raw)
In-Reply-To: <85c1d945-d49b-3350-6ff4-a058c5a8c1d7@arm.com>
> What's your overall setup? So far with my RK3328 box I've found that
> with an IPv4 link and an MTU of 2000 I have to dial PBL right down to
> 1 or 2 (with no-pbl-x8 as well) to prevent Tx stalling, and with the
> MTU bumped up to 3000 it just won't play at any PBL setting...
>
> Robin.
I'm using a Libre Computer Renegade with RK3328 SoC(maybe it's a board
specific thing?)
I'm using txpbl as from what I can gather, the rx has no issues, no
need to change it.
When it comes to rx,
running the server (iperf3 -s) on the Renegade and iperf3 -c
<renegade_ip> on my laptop,
I get about 940 Mbps. It's always been like that, satisfactory.
When it comes to tx (the one all the fuss is about)
I eventually find that just with snps,txpbl = <0x21>, and no other pbl
thing set I get about 905 Mbps on average sent to my laptop, now
running the iperf3 server.
I must say I haven't touched the MTUs but I never needed to as the
issue presented itself in normal usage. Simple iperf tests will fail
after same kilobytes if no tweaks are applied.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-04-05 18:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 18:18 [PATCH 1/2] stmmac: introduce flag to dynamically disable TX offload for rockchip devices Leonidas P. Papadakos
2019-04-01 18:31 ` Heiko Stübner
2019-04-01 18:54 ` Robin Murphy
2019-04-01 19:06 ` Heiko Stübner
2019-04-01 19:12 ` Philipp Tomsich
2019-04-02 7:59 ` Jose Abreu
2019-04-02 11:49 ` Robin Murphy
2019-04-02 11:53 ` Jose Abreu
2019-04-02 22:08 ` Robin Murphy
2019-04-02 22:48 ` Leonidas P. Papadakos
2019-04-03 7:55 ` Jose Abreu
2019-04-03 15:35 ` Leonidas P. Papadakos
2019-04-03 15:55 ` Leonidas P. Papadakos
2019-04-03 16:12 ` Robin Murphy
2019-04-05 10:24 ` Jose Abreu
2019-04-05 17:58 ` Leonidas P. Papadakos
2019-04-05 18:14 ` Leonidas P. Papadakos
2019-04-05 18:29 ` Robin Murphy
2019-04-05 18:38 ` Leonidas P. Papadakos [this message]
2019-04-11 21:09 ` Leonidas P. Papadakos
2019-04-12 7:35 ` Jose Abreu
2019-04-12 11:13 ` Leonidas P. Papadakos
2019-04-15 8:15 ` Jose Abreu
2019-04-15 21:45 ` Leonidas P. Papadakos
2019-04-15 22:19 ` Leonidas P. Papadakos
2019-04-16 8:01 ` Jose Abreu
2019-04-16 10:03 ` Leonidas P. Papadakos
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=1554489537.1199.0@gmail.com \
--to=papadakospan@gmail.com \
--cc=alexandre.torgue@st.com \
--cc=christoph.muellner@theobroma-systems.com \
--cc=heiko@sntech.de \
--cc=jose.abreu@synopsys.com \
--cc=klaus.goger@theobroma-systems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=philipp.tomsich@theobroma-systems.com \
--cc=robin.murphy@arm.com \
/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).