linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Leonidas P. Papadakos" <papadakospan@gmail.com>
To: Jose Abreu <jose.abreu@synopsys.com>
Cc: "Robin Murphy" <robin.murphy@arm.com>,
	"Philipp Tomsich" <philipp.tomsich@theobroma-systems.com>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Christoph Müllner" <christoph.muellner@theobroma-systems.com>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@st.com>,
	netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
	"Klaus Goger" <klaus.goger@theobroma-systems.com>
Subject: RE: [PATCH 1/2] stmmac: introduce flag to dynamically disable TX offload for rockchip devices
Date: Tue, 16 Apr 2019 13:03:37 +0300	[thread overview]
Message-ID: <1555409017.1234.0@gmail.com> (raw)
In-Reply-To: <78EB27739596EE489E55E81C33FEC33A0B45B252@DE02WEMBXB.internal.synopsys.com>


txpbl <0x4> (without the no-pbl-x8 option) is the last value where I 
can change the MTU without a timeout.
I've also tried <0x20> with and without no-pbl-x8 but in that area MTU 
is a hot potato.

Seems pretty good though, I'll keep poking to see if it's stable.
currently at txbpl <0x4> by iself I get tx max 934 average 916 Mbps

IT does fluctuate at times but mostly there.



      reply	other threads:[~2019-04-16 10:03 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
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 [this message]

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=1555409017.1234.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).