Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp4893760rwl; Mon, 10 Apr 2023 19:32:01 -0700 (PDT) X-Google-Smtp-Source: AKy350a9ugR5B8XQYqZJ9aUc6eDYv5SQfz2m0+BS56tQ06cfz5TQoXvFMu90yeFWjxPC9k+QtbC2 X-Received: by 2002:a05:6a20:a9a0:b0:cc:fa4b:3a6a with SMTP id cc32-20020a056a20a9a000b000ccfa4b3a6amr12275512pzb.58.1681180321416; Mon, 10 Apr 2023 19:32:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1681180321; cv=none; d=google.com; s=arc-20160816; b=vlfFScNaKOsC+9QYjb8w+K770oBO24dcWhGhVUm4hEChgetDJtP3yt7e+myTPcTWaV wl+8pIyi7RPhUahzVbzIb/xFM8pkmajU4um+so6AnE9kzgkXmxD8/keRc6Ep83a7TbJh oidWIPaBQxaVeAil2M1F7sonWa4zQcUkcKeFiSYcQi4l5jSEqtBRPuOHTG/Pza+yv2Lk 7p7EuDikxVIAgzLIOYj8elm0MEfyGTyOqMjPYGE3EMU9kqD3v+YmNdlqnWnBwVJwjBJV JFQmxf7QzZLPsgC6E60fmZE2uBQHycvAP+iE1IdfF2BCSTQ/xyqpMPTO9W5weikK6BHm Mamg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=4/pq0kfRsZZRdtz49/VrpJy5R/A4i/UsofZV+uwwKy8=; b=KFwaTVOjgsqx2Vp57Mb3Y5F5+xyrJHG1BN2eT4JZX9HvPjQt8QUABLMFcwnS+Xui7u OFUpyqYfm2HwUer48MDRZVG6aI+1pXDb7UpsBR97omxG5b5IBlJ8ld938tnyMpsyJw93 FZn7NQ4gk+ddIK8s58XyZbECyqQKe88W9QK74UW29bS+5vR+25Lx0IkbmJ63eEbz5t7Z G+iLty0/h4XAxjfITY6YOHmF0F9TJdlDXEZXQlTc26WjAck+wdOwl8w3DVFEdJWOcffy 2fsyzsIEuc//ncrSMuLRLEdLmYyS59uloDONcS3fOY/yKYidf7f5pAIPTVrmPKuQhW9x p5/w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=Aowq6Z9l; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f23-20020a63e317000000b0050f817c6c82si3731673pgh.232.2023.04.10.19.31.49; Mon, 10 Apr 2023 19:32:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=Aowq6Z9l; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229697AbjDKCTV (ORCPT + 99 others); Mon, 10 Apr 2023 22:19:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57448 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229656AbjDKCTT (ORCPT ); Mon, 10 Apr 2023 22:19:19 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 260781738; Mon, 10 Apr 2023 19:19:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=4/pq0kfRsZZRdtz49/VrpJy5R/A4i/UsofZV+uwwKy8=; b=Aowq6Z9l2xa7L35kAFEsWHwI0D 7TVFqAMffBofjnx1A48CSm1uMv9/PcGC6TaJWYf7lTJBbz7UQJY6Pag0HTvD/jgXB8wp1JKPD57hU gmtwJujaQq+liSXcqsFxA6rvtdT53zjXwHARfiXKyQrmFDyu06hOX011MTMIBW8ZDIR0=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1pm3b4-009xAV-WB; Tue, 11 Apr 2023 04:19:03 +0200 Date: Tue, 11 Apr 2023 04:19:02 +0200 From: Andrew Lunn To: Liang Li Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, Paolo Abeni , ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org, john.fastabend@gmail.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Hangbin Liu , "Toppins, Jonathan" Subject: Re: [Question] About bonding offload Message-ID: <49e0cf25-331b-4d26-8d9a-66434e7a270e@lunn.ch> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 11, 2023 at 09:47:14AM +0800, Liang Li wrote: > Hi Everyone, > > I'm a redhat network-qe and am testing bonding offload. e.g. gso,tso,gro,lro. > I got two questions during my testing. > > 1. The tcp performance has no difference when bonding GRO is on versus off. > When testing with bonding, I always get ~890 Mbits/sec bandwidth no > matter whether GRO is on. > When testing with a physical NIC instead of bonding on the same > machine, with GRO off, I get 464 Mbits/sec bandwidth, with GRO on, I > get 897 Mbits/sec bandwidth. > So looks like the GRO can't be turned off on bonding? > > I used iperf3 to test performance. > And I limited iperf3 process cpu usage during my testing to simulate a > cpu bottleneck. > Otherwise it's difficult to see bandwidth differences when offload is > on versus off. > > I reported a bz for this: https://bugzilla.redhat.com/show_bug.cgi?id=2183434 > > 2. Should bonding propagate offload configuration to slaves? > For now, only "ethtool -K bond0 lro off" can be propagated to slaves, > others can't be propagated to slaves, e.g. > ethtool -K bond0 tso on/off > ethtool -K bond0 gso on/off > ethtool -K bond0 gro on/off > ethtool -K bond0 lro on > All above configurations can't be propagated to bonding slaves. > > I reports a bz for this: https://bugzilla.redhat.com/show_bug.cgi?id=2183777 > > I am using the RHEL with kernel 4.18.0-481.el8.x86_64. Hi Liang Can you reproduce these issues with a modern kernel? net-next, or 6.3? The normal process for issues like this is to investigate with the latest kernel, and then backport fixes to old stable kernels. Andrew