From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Greear Subject: Re: TCP reaching to maximum throughput after a long time Date: Tue, 12 Apr 2016 08:04:52 -0700 Message-ID: <570D0E94.3080006@candelatech.com> References: <1460472764.6473.589.camel@edumazet-glaptop3.roam.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Eric Dumazet , "David S. Miller" , Eric Dumazet , Neal Cardwell , Yuchung Cheng , Nandita Dukkipati , open list , "Kama, Meirav" To: "Machani, Yaniv" , netdev Return-path: In-Reply-To: <1460472764.6473.589.camel@edumazet-glaptop3.roam.corp.google.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On 04/12/2016 07:52 AM, Eric Dumazet wrote: > On Tue, 2016-04-12 at 12:17 +0000, Machani, Yaniv wrote: >> Hi, >> After updating from Kernel 3.14 to Kernel 4.4 we have seen a TCP performance degradation over Wi-Fi. >> In 3.14 kernel, TCP got to its max throughout after less than a second, while in the 4.4 it is taking ~20-30 seconds. >> UDP TX/RX and TCP RX performance is as expected. >> We are using a Beagle Bone Black and a WiLink8 device. >> >> Were there any related changes that might cause such behavior ? >> Kernel configuration and sysctl values were compared, but no significant differences have been found. If you are using 'Cubic' TCP congestion control, then please try something different. It was broken last I checked, at least when used with the ath10k driver. https://marc.info/?l=linux-netdev&m=144405216005715&w=2 Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com