Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751947AbcDMU0l (ORCPT <rfc822;w@1wt.eu>);
	Wed, 13 Apr 2016 16:26:41 -0400
Received: from bear.ext.ti.com ([192.94.94.41]:36665 "EHLO bear.ext.ti.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751827AbcDMU0j (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 13 Apr 2016 16:26:39 -0400
From: "Machani, Yaniv" <yanivma@ti.com>
To: Neal Cardwell <ncardwell@google.com>,
        Eric Dumazet <eric.dumazet@gmail.com>
CC: Yuchung Cheng <ycheng@google.com>, Ben Greear <greearb@candelatech.com>,
        netdev <netdev@vger.kernel.org>,
        "David S. Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Nandita Dukkipati <nanditad@google.com>,
        open list <linux-kernel@vger.kernel.org>,
        "Kama, Meirav" <meiravk@ti.com>
Subject: RE: TCP reaching to maximum throughput after a long time
Thread-Topic: TCP reaching to maximum throughput after a long time
Thread-Index: AdGUtUgUUC2AurLuQ6Wg1hy5fbMrTQABOykAAABsewAADUV+wP//63eAgAABuYCAAAGsAIAAAc6AgAATmoCAAFuhAIAABtCAgAC4Z4D//3x84A==
Date: Wed, 13 Apr 2016 20:26:32 +0000
Message-ID: <AE1C82FB3D0EC64DB1F752C81CBD110139106E71@DFRE01.ent.ti.com>
References: <AE1C82FB3D0EC64DB1F752C81CBD110139100057@DFRE01.ent.ti.com>
	<1460472764.6473.589.camel@edumazet-glaptop3.roam.corp.google.com>
	<570D0E94.3080006@candelatech.com>
	<AE1C82FB3D0EC64DB1F752C81CBD110139101889@DFRE01.ent.ti.com>
	<570D566B.8050302@candelatech.com>
	<1460492253.6473.596.camel@edumazet-glaptop3.roam.corp.google.com>
	<570D5944.5070100@candelatech.com>
	<1460492999.6473.599.camel@edumazet-glaptop3.roam.corp.google.com>
	<570D6B39.3050605@candelatech.com>
	<CAK6E8=f+4BagGi5BzLER=Hn2dDJ5FHWkEqLq=04tnWResk58GQ@mail.gmail.com>
	<1460518349.32504.8.camel@edumazet-glaptop3.roam.corp.google.com>
 <CADVnQy=1eZbWxLRJ3t8grazBJzQrF6LjudiX3HF3sG=sNmGq5Q@mail.gmail.com>
In-Reply-To: <CADVnQy=1eZbWxLRJ3t8grazBJzQrF6LjudiX3HF3sG=sNmGq5Q@mail.gmail.com>
Accept-Language: en-US, he-IL
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.167.188.42]
x-exclaimer-md-config: f9c360f5-3d1e-4c3c-8703-f45bf52eff6b
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u3DKQmOb021822
Content-Length: 1357
Lines: 56

On Wed, Apr 13, 2016 at 17:32:29, Neal Cardwell wrote:
> Miller; Eric Dumazet; Nandita Dukkipati; open list; Kama, Meirav
> Subject: Re: TCP reaching to maximum throughput after a long time
> 
> I like the idea to disable hystart ack-train.
> 
> 
> Yaniv, can you please re-run your test with CUBIC in three different
> scenarios:
> 
> a) echo 0 > /sys/module/tcp_cubic/parameters/hystart_detect
This fixes the issues, got to max throughput immediately. 

> 
> b) echo 1 > /sys/module/tcp_cubic/parameters/hystart_detect
> 
This shows the same results as before, starting low and increasing slowly.

>
> c) echo 2 > /sys/module/tcp_cubic/parameters/hystart_detect
This gets us a bit higher at the beginning, but never (waited ~60 sec) goes to the max.


Appreciate your help on this.
Yaniv
> 
> 
> This should help us isolate whether the hystart ack-train algorithm is 
> causing problems in this particular case.
> 
> Thanks!
> neal
> 
> 
> 
> On Tue, Apr 12, 2016 at 11:32 PM, Eric Dumazet 
> <eric.dumazet@gmail.com>
> wrote:
> 
> 
> 	On Tue, 2016-04-12 at 20:08 -0700, Yuchung Cheng wrote:
> 
> 	> based on the prev thread I propose we disable hystart ack-train. It 
> is
> 	> brittle under various circumstances. We've disabled that at Google 
> for
> 	> years.
> 
> 	Right, but because we also use sch_fq packet scheduler and pacing ;)
> 
> 
> 
>