From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A7EACC122 for ; Wed, 28 Jun 2023 14:19:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 98BCFC433C8; Wed, 28 Jun 2023 14:19:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1687961972; bh=yrVlAWiwxFJi/PSUnLEvi1oEGkS0sNHufr0RPMimCWE=; h=Date:Subject:To:References:From:In-Reply-To:From; b=YM1IppAygzGHN4bX7d7k6Q2VpMqf5//MszBZC+ih6wU75AtTQ74afbl1qmk+6t1Rv MMVMDEyz45sK6IV5iE2ddrwcMiNbbnK7+EMYQXQtuAeNXwDLzyFUlvbpdQoIXLklzp HEfAtDBLEossqE8WvxDajNU1kRioww6Cf1sRB441Kweah2/4Unnb/TzGEwADLZnUPA X8aiQIQXw0eizjV037noLjdItbiQFa0LaTE2BrptArYy0HBQph5tfeq4qPcNqaE8Lp P5md2kIb6rlvkoc0SzH2s1BEPc2kB0Bc7ubHbUnDB2iPlK99S6iZ+/5jSsvdsDmSkg SrPLI/4D9xOPg== Message-ID: Date: Wed, 28 Jun 2023 08:19:30 -0600 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.12.0 Subject: Re: [PATCH v3 1/1] gro: decrease size of CB To: Gal Pressman , Richard Gobert , davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, aleksander.lobakin@intel.com, lixiaoyan@google.com, lucien.xin@gmail.com, alexanderduyck@fb.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230601160924.GA9194@debian> <20230601161407.GA9253@debian> Content-Language: en-US From: David Ahern In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 6/28/23 6:42 AM, Gal Pressman wrote: > On 27/06/2023 17:21, David Ahern wrote: >> On 6/26/23 2:55 AM, Gal Pressman wrote: >>> I believe this commit broke gro over udp tunnels. >>> I'm running iperf tcp traffic over geneve interfaces and the bandwidth >>> is pretty much zero. >>> >> >> Could you add a test script to tools/testing/selftests/net? It will help >> catch future regressions. >> > > I'm checking internally, someone from the team might be able to work on > this, though I'm not sure that a test that verifies bandwidth makes much > sense as a selftest. > With veth and namespaces I expect up to 25-30G performance levels, depending on the test. When something fundamental breaks like this patch a drop to < 1G would be a red flag, so there is value to the test.