From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-17.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AF5EDC433DB for ; Tue, 9 Mar 2021 10:25:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8298F6526C for ; Tue, 9 Mar 2021 10:25:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229520AbhCIKZR (ORCPT ); Tue, 9 Mar 2021 05:25:17 -0500 Received: from mail.kernel.org ([198.145.29.99]:40362 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230397AbhCIKY6 (ORCPT ); Tue, 9 Mar 2021 05:24:58 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 74D7A65267; Tue, 9 Mar 2021 10:24:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1615285497; bh=2FySe3IdViQoNOxMsg2eQz0XxJtl7VvrMzQyzOkLadY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=M18I/r2rmD5M6No15HFslUeY1q2i8S3zhscak7Ae/xK/jTjMzh1HZ5mVLlShuayAm uEQoYU27AFpYkjtVA5AtfOCibSOy2lHCklS50LfF5Ovcb/zBlN7aqkEPJcorIV2Po1 Dp3Dv0judbh5ADnhFKc/nZDy5hDN0bsE7VxR0WE520AHORBk62kItnutlXqyj+o8bx 2CTsVnVJCIYNcWmhH7fb9w1yNsrb3wi3LMmG2YdxIEiqtqoi4pjFdUX/UuXrng74S8 SjqXI7in5ny0xy1foIUAYhDf8fOkykdjA/bt3jg/pIKHOGMKOuraxRtkbXX/T4MCyQ iuAJ3u4a0SNPw== Received: by pali.im (Postfix) id 2F9AB89E; Tue, 9 Mar 2021 11:24:55 +0100 (CET) Date: Tue, 9 Mar 2021 11:24:55 +0100 From: Pali =?utf-8?B?Um9ow6Fy?= To: Greg KH Cc: stable@vger.kernel.org, Alexander Lobakin , "David S . Miller" , Marek =?utf-8?B?QmVow7pu?= Subject: Re: [PATCH] net: dsa: add GRO support via gro_cells Message-ID: <20210309102455.qxwu7sokv2qhcz46@pali> References: <20210308175757.8373-1-pali@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: NeoMutt/20180716 Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Monday 08 March 2021 20:55:20 Greg KH wrote: > On Mon, Mar 08, 2021 at 06:57:57PM +0100, Pali Rohár wrote: > > From: Alexander Lobakin > > > > commit e131a5634830047923c694b4ce0c3b31745ff01b upstream. > > > > gro_cells lib is used by different encapsulating netdevices, such as > > geneve, macsec, vxlan etc. to speed up decapsulated traffic processing. > > CPU tag is a sort of "encapsulation", and we can use the same mechs to > > greatly improve overall DSA performance. > > skbs are passed to the GRO layer after removing CPU tags, so we don't > > need any new packet offload types as it was firstly proposed by me in > > the first GRO-over-DSA variant [1]. > > > > The size of struct gro_cells is sizeof(void *), so hot struct > > dsa_slave_priv becomes only 4/8 bytes bigger, and all critical fields > > remain in one 32-byte cacheline. > > The other positive side effect is that drivers for network devices > > that can be shipped as CPU ports of DSA-driven switches can now use > > napi_gro_frags() to pass skbs to kernel. Packets built that way are > > completely non-linear and are likely being dropped without GRO. > > > > This was tested on to-be-mainlined-soon Ethernet driver that uses > > napi_gro_frags(), and the overall performance was on par with the > > variant from [1], sometimes even better due to minimal overhead. > > net.core.gro_normal_batch tuning may help to push it to the limit > > on particular setups and platforms. > > > > iperf3 IPoE VLAN NAT TCP forwarding (port1.218 -> port0) setup > > on 1.2 GHz MIPS board: > > > > 5.7-rc2 baseline: > > > > [ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-120.01 sec 9.00 GBytes 644 Mbits/sec 413 sender > > [ 5] 0.00-120.00 sec 8.99 GBytes 644 Mbits/sec receiver > > > > Iface RX packets TX packets > > eth0 7097731 7097702 > > port0 426050 6671829 > > port1 6671681 425862 > > port1.218 6671677 425851 > > > > With this patch: > > > > [ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-120.01 sec 12.2 GBytes 870 Mbits/sec 122 sender > > [ 5] 0.00-120.00 sec 12.2 GBytes 870 Mbits/sec receiver > > > > Iface RX packets TX packets > > eth0 9474792 9474777 > > port0 455200 353288 > > port1 9019592 455035 > > port1.218 353144 455024 > > > > v2: > > - Add some performance examples in the commit message; > > - No functional changes. > > > > [1] https://lore.kernel.org/netdev/20191230143028.27313-1-alobakin@dlink.ru/ > > > > Signed-off-by: Alexander Lobakin > > Signed-off-by: David S. Miller > > > > --- > > This patch radically increase network performance on DSA setup. > > > > Please include this patch into stable releases. > > > > I have done following tests: > > > > NAT is a tested Espressobin board (ARM64 Marvell Armada 3720 SoC with > > Marvell 88E6141 DSA switch) which was configured for IPv4 masquerade. > > WAN and LAN are another two static boxes on which was running iperf3. > > > > 4.19.179 without e131a5634830047923c694b4ce0c3b31745ff01b > > > > WAN --> NAT --> LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.01 sec 440 MBytes 369 Mbits/sec 12 sender > > [ 5] 0.00-10.00 sec 437 MBytes 367 Mbits/sec receiver > > > > WAN <-- NAT <-- LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.00 sec 390 MBytes 327 Mbits/sec 90 sender > > [ 5] 0.00-10.01 sec 388 MBytes 326 Mbits/sec receiver > > > > 4.19.179 with e131a5634830047923c694b4ce0c3b31745ff01b > > > > WAN --> NAT --> LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.01 sec 616 MBytes 516 Mbits/sec 18 sender > > [ 5] 0.00-10.00 sec 613 MBytes 515 Mbits/sec receiver > > > > WAN <-- NAT <-- LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.00 sec 573 MBytes 480 Mbits/sec 32 sender > > [ 5] 0.00-10.01 sec 570 MBytes 478 Mbits/sec receiver > > > > 5.4.103 without e131a5634830047923c694b4ce0c3b31745ff01b > > > > WAN --> NAT --> LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.01 sec 454 MBytes 380 Mbits/sec 62 sender > > [ 5] 0.00-10.00 sec 451 MBytes 378 Mbits/sec receiver > > > > WAN <-- NAT <-- LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.00 sec 425 MBytes 356 Mbits/sec 155 sender > > [ 5] 0.00-10.01 sec 422 MBytes 354 Mbits/sec receiver > > > > 5.4.103 with e131a5634830047923c694b4ce0c3b31745ff01b > > > > WAN --> NAT --> LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.01 sec 604 MBytes 506 Mbits/sec 8 sender > > [ 5] 0.00-10.00 sec 601 MBytes 504 Mbits/sec receiver > > > > WAN <-- NAT <-- LAN > > [ ID] Interval Transfer Bitrate Retr > > [ 5] 0.00-10.00 sec 578 MBytes 485 Mbits/sec 79 sender > > [ 5] 0.00-10.01 sec 575 MBytes 482 Mbits/sec receiver > > --- > > net/dsa/Kconfig | 1 + > > net/dsa/dsa.c | 2 +- > > net/dsa/dsa_priv.h | 3 +++ > > net/dsa/slave.c | 10 +++++++++- > > 4 files changed, 14 insertions(+), 2 deletions(-) > > So this patch should be applied to the 4.19 and 5.4 stable queues? Yes! Patch was introduced in 5.8 and applies cleanly for 4.19 and 5.4 stable releases without any modifications. Trying to apply it for 4.14 results in patch conflicts. So I have done tests only for 4.19 and 5.4. > Speed increases like this are always nice to see :) > > thanks, > > greg k-h