From: "Tobias Waldekranz" <tobias@waldekranz.com>
To: "Andy Duan" <fugang.duan@nxp.com>, "David Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [EXT] Re: [PATCH net-next] net: ethernet: fec: prevent tx starvation under high rx load
Date: Tue, 30 Jun 2020 15:45:51 +0200 [thread overview]
Message-ID: <C3UHDOU16UJF.1HSCO9KJ9CIRG@wkz-x280> (raw)
In-Reply-To: <AM6PR0402MB36074675DB9DBCD9788DCE9BFF6F0@AM6PR0402MB3607.eurprd04.prod.outlook.com>
On Tue Jun 30, 2020 at 11:47 AM CEST, Andy Duan wrote:
> Tobias, sorry, I am not running the net tree, I run the linux-imx tree:
> https://source.codeaurora.org/external/imx/linux-imx/refs/heads
> branch：imx_5.4.24_2.1.0
> But the data follow is the same as net tree.
I've now built the same kernel. On this one the issue does not occur,
consistent throughput of ~940Mbps just like you're seeing.
Now moving to mainline 5.4 to rule out any NXP changes first, then
start bisecting.
prev parent reply other threads:[~2020-06-30 14:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 8:57 [PATCH net-next] net: ethernet: fec: prevent tx starvation under high rx load Tobias Waldekranz
2020-06-25 19:19 ` David Miller
2020-06-28 6:23 ` [EXT] " Andy Duan
2020-06-29 16:29 ` Tobias Waldekranz
2020-06-30 6:27 ` Andy Duan
2020-06-30 7:30 ` Tobias Waldekranz
2020-06-30 8:26 ` Andy Duan
2020-06-30 8:55 ` Tobias Waldekranz
2020-06-30 9:02 ` Andy Duan
2020-06-30 9:12 ` Tobias Waldekranz
2020-06-30 9:47 ` Andy Duan
2020-06-30 11:01 ` Tobias Waldekranz
2020-07-01 1:27 ` Andy Duan
2020-06-30 13:45 ` Tobias Waldekranz [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=C3UHDOU16UJF.1HSCO9KJ9CIRG@wkz-x280 \
--to=tobias@waldekranz.com \
--cc=davem@davemloft.net \
--cc=fugang.duan@nxp.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