From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleksandr Natalenko Subject: Re: TCP and BBR: reproducibly low cwnd and bandwidth Date: Fri, 16 Feb 2018 23:50:55 +0100 Message-ID: <7409814.oObJlsYiIU@natalenko.name> References: <1697118.nv5eASg0nx@natalenko.name> <1555524.zWX3teDkM3@natalenko.name> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: Neal Cardwell , Eric Dumazet , "David S. Miller" , Netdev , Yuchung Cheng , Soheil Hassas Yeganeh , Jerry Chu , Dave Taht To: Eric Dumazet Return-path: Received: from vulcan.natalenko.name ([104.207.131.136]:56498 "EHLO vulcan.natalenko.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751125AbeBPWu6 (ORCPT ); Fri, 16 Feb 2018 17:50:58 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: Hi. On p=E1tek 16. =FAnora 2018 21:54:05 CET Eric Dumazet wrote: > /* snip */ > Something fishy really : > /* snip */ > Not only the receiver suddenly adds a 25 ms delay, but also note that > it acknowledges all prior segments (ack 112949), but with a wrong ecr > value ( 2327043753 ) > instead of 2327043759 > /* snip */ Eric has encouraged me to look closer at what's there in the ethtool, and I= 've=20 just had a free time to play with it. I've found out that enabling scatter- gather (ethtool -K enp3s0 sg on, it is disabled by default on both hosts)=20 brings the throughput back to normal even with BBR+fq_codel. Whyyyy? What's the deal BBR has with sg? Oleksandr