From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <netdev-owner@vger.kernel.org>
Received: from vulcan.natalenko.name ([104.207.131.136]:38232 "EHLO
        vulcan.natalenko.name" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752441AbeBTTfR (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 20 Feb 2018 14:35:17 -0500
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
        "David S . Miller" <davem@davemloft.net>,
        netdev <netdev@vger.kernel.org>,
        Neal Cardwell <ncardwell@google.com>,
        Yuchung Cheng <ycheng@google.com>,
        Soheil Hassas Yeganeh <soheil@google.com>
Subject: Re: [PATCH net-next 0/6] tcp: remove non GSO code
Date: Tue, 20 Feb 2018 20:35:14 +0100
Message-ID: <4964697.hB4CnsZvNY@natalenko.name>
In-Reply-To: <1519153062.55655.24.camel@gmail.com>
References: <20180219195652.242663-1-edumazet@google.com> <1519141172.55655.21.camel@gmail.com> <1519153062.55655.24.camel@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

Hi.

On =FAter=FD 20. =FAnora 2018 19:57:42 CET Eric Dumazet wrote:
> Actually timer drifts are not horrible (at least on my lab hosts)
>=20
> But BBR has a pessimistic way to sense the burst size, as it is tied to
> TSO/GSO being there.
>=20
> Following patch helps a lot.

Not really, at least if applied to v4.15.4. Still getting 2 Gbps less betwe=
en=20
VMs if using BBR instead of Reno.

Am I doing something wrong?

Oleksandr