From: Jisheng.Zhang@synaptics.com (Jisheng Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 6/7] net: mvneta: Don't use GRO on Armada 3720
Date: Thu, 9 Aug 2018 12:40:41 +0800 [thread overview]
Message-ID: <20180809124022.790f1784@xhacker.debian> (raw)
In-Reply-To: <20180808152706.21727-7-marek.behun@nic.cz>
+ more people
On Wed, 8 Aug 2018 17:27:05 +0200 Marek Beh?n wrote:
> For some reason on Armada 3720 boards (EspressoBin and Turris Mox) the
> networking driver behaves weirdly when using napi_gro_receive.
>
> For example downloading a big file from a local network (low ping) is
> fast, but when downloading from a remote server (higher ping), the
> download speed is at first high but drops rapidly to almost nothing or
> absolutely nothing.
We also met this issue on some berlin platforms. I tried to fix the bug,
but no clue so far.
>
> This is fixed when using netif_receive_skb instead of napi_gro_receive.
This is a workaround. The good news is this workaround also fixes the issue
we saw on berlin.
>
> Signed-off-by: Marek Behun <marek.behun@nic.cz>
> Cc: Russell King - ARM Linux <linux@armlinux.org.uk>
> Cc: netdev at vger.kernel.org
>
> diff --git a/drivers/net/ethernet/marvell/mvneta.c b/drivers/net/ethernet/marvell/mvneta.c
> index 0ad2f3f7da85..27f3017d94c5 100644
> --- a/drivers/net/ethernet/marvell/mvneta.c
> +++ b/drivers/net/ethernet/marvell/mvneta.c
> @@ -1959,7 +1959,10 @@ static int mvneta_rx_swbm(struct mvneta_port *pp, int rx_todo,
>
> skb->protocol = eth_type_trans(skb, dev);
> mvneta_rx_csum(pp, rx_status, skb);
> - napi_gro_receive(&port->napi, skb);
> + if (pp->neta_armada3700)
> + netif_receive_skb(skb);
> + else
> + napi_gro_receive(&port->napi, skb);
>
> rcvd_pkts++;
> rcvd_bytes += rx_bytes;
> @@ -2001,7 +2004,10 @@ static int mvneta_rx_swbm(struct mvneta_port *pp, int rx_todo,
>
> mvneta_rx_csum(pp, rx_status, skb);
>
> - napi_gro_receive(&port->napi, skb);
> + if (pp->neta_armada3700)
> + netif_receive_skb(skb);
> + else
> + napi_gro_receive(&port->napi, skb);
> }
>
> if (rcvd_pkts) {
next prev parent reply other threads:[~2018-08-09 4:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 15:26 [PATCH v1 0/7] Add support for the Turris Mox router Marek Behún
2018-08-08 15:27 ` [PATCH v1 1/7] From: Ken Ma <make@marvell.com> Marek Behún
2018-08-08 16:49 ` Andrew Lunn
2018-08-08 15:27 ` [PATCH v1 2/7] drivers: mfd: Add support for Moxtet bus Marek Behún
2018-08-08 15:32 ` Marek Behún
2018-08-08 15:27 ` [PATCH v1 3/7] drivers: gpio: Add support for Turris Mox SFP GPIOs Marek Behún
2018-08-08 16:55 ` Andrew Lunn
2018-08-08 20:40 ` Marek Behun
2018-08-08 15:27 ` [PATCH v1 4/7] watchdog: Add support for Armada 37xx CPU watchdog Marek Behún
2018-08-08 15:27 ` [PATCH v1 5/7] arm64: dts: marvell: armada-37xx: add nodes to support watchdog Marek Behún
2018-08-08 15:27 ` [PATCH v1 6/7] net: mvneta: Don't use GRO on Armada 3720 Marek Behún
2018-08-08 16:58 ` Andrew Lunn
2018-08-08 17:57 ` Dave Taht
2018-08-09 4:40 ` Jisheng Zhang [this message]
2018-08-09 11:27 ` Jisheng Zhang
2018-08-09 12:08 ` Jisheng Zhang
2018-08-21 10:07 ` Marek Behún
2018-08-08 15:27 ` [PATCH v1 7/7] ARM64: dts: marvell: Add DTS files for Turris Mox Marek Behún
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=20180809124022.790f1784@xhacker.debian \
--to=jisheng.zhang@synaptics.com \
--cc=linux-arm-kernel@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 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).