From: "Rafał Miłecki" <zajec5@gmail.com>
To: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Cc: Stefano Brivio <sbrivio@redhat.com>,
Sabrina Dubroca <sd@queasysnail.net>,
David Ahern <dsahern@gmail.com>, Felix Fietkau <nbd@nbd.name>,
Jo-Philipp Wich <jo@mein.io>,
Koen Vandeputte <koen.vandeputte@ncentric.com>
Subject: NAT performance regression caused by vlan GRO support
Date: Thu, 4 Apr 2019 14:57:15 +0200 [thread overview]
Message-ID: <73223229-6bc0-2647-6952-975961811866@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
Hello,
I'd like to report a regression that goes back to the 2015. I know it's damn
late, but the good thing is, the regression is still easy to reproduce, verify &
revert.
Long story short, starting with the commit 66e5133f19e9 ("vlan: Add GRO support
for non hardware accelerated vlan") - which first hit kernel 4.2 - NAT
performance of my router dropped by 30% - 40%.
My hardware is BCM47094 SoC (dual core ARM) with integrated network controller
and external BCM53012 switch.
Relevant setup:
* SoC network controller is wired to the hardware switch
* Switch passes 802.1q frames with VID 1 to four LAN ports
* Switch passes 802.1q frames with VID 2 to WAN port
* Linux does NAT for LAN (eth0.1) to WAN (eth0.2)
* Linux uses pfifo and "echo 2 > rps_cpus"
* Ryzen 5 PRO 2500U (x86_64) laptop connected to a LAN port
* Intel i7-2670QM laptop connected to a WAN port
* Speed of LAN to WAN measured using iperf & TCP over 10 minutes
1) 5.1.0-rc3
[ 6] 0.0-600.0 sec 39.9 GBytes 572 Mbits/sec
2) 5.1.0-rc3 + rtcache patch
[ 6] 0.0-600.0 sec 40.0 GBytes 572 Mbits/sec
3) 5.1.0-rc3 + disable GRO support
[ 6] 0.0-300.4 sec 27.5 GBytes 786 Mbits/sec
4) 5.1.0-rc3 + rtcache patch + disable GRO support
[ 6] 0.0-600.0 sec 65.6 GBytes 939 Mbits/sec
5) 4.1.15 + rtcache patch
934 Mb/s
6) 4.3.4 + rtcache patch
565 Mb/s
As you can see I can achieve a big performance gain by disabling/reverting a
GRO support. Getting up to 65% faster NAT makes a huge difference and ideally
I'd like to get that with upstream Linux code.
Could someone help me and check the reported commit/code, please? Is there
any other info I can provide or anything I can test for you?
--- a/net/8021q/vlan_core.c
+++ b/net/8021q/vlan_core.c
@@ -545,6 +545,8 @@ static int __init vlan_offload_init(void)
{
unsigned int i;
+ return -ENOTSUPP;
+
for (i = 0; i < ARRAY_SIZE(vlan_packet_offloads); i++)
dev_add_offload(&vlan_packet_offloads[i]);
[-- Attachment #2: .config --]
[-- Type: application/x-config, Size: 77368 bytes --]
next reply other threads:[~2019-04-04 12:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 12:57 Rafał Miłecki [this message]
2019-04-04 15:17 ` NAT performance regression caused by vlan GRO support Toshiaki Makita
2019-04-04 20:22 ` Rafał Miłecki
2019-04-05 4:26 ` Toshiaki Makita
2019-04-05 5:48 ` Rafał Miłecki
2019-04-05 7:11 ` Rafał Miłecki
2019-04-05 7:14 ` Felix Fietkau
2019-04-05 7:58 ` Toshiaki Makita
2019-04-05 8:12 ` Rafał Miłecki
2019-04-05 8:24 ` Rafał Miłecki
2019-04-05 10:18 ` Toke Høiland-Jørgensen
2019-04-05 10:51 ` Florian Westphal
2019-04-05 11:00 ` Eric Dumazet
2019-04-07 11:53 ` Rafał Miłecki
2019-04-07 11:54 ` Rafał Miłecki
2019-04-08 13:31 ` David Laight
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=73223229-6bc0-2647-6952-975961811866@gmail.com \
--to=zajec5@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=jo@mein.io \
--cc=koen.vandeputte@ncentric.com \
--cc=makita.toshiaki@lab.ntt.co.jp \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.