[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1508089409.31614.74.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Sun, 15 Oct 2017 10:43:29 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Natale Patriciello <natale.patriciello@...il.com>
Cc: "David S . Miller" <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Ahmed Said <ahmed.said@...roma2.it>,
Francesco Zampognaro <zampognaro@....uniroma2.it>,
Cesare Roseti <roseti@....uniroma2.it>
Subject: Re: [RFC PATCH v2 5/5] wave: Added TCP Wave
On Sat, 2017-10-14 at 13:47 +0200, Natale Patriciello wrote:
> TCP Wave (TCPW) replaces the window-based transmission paradigm of the
> standard TCP with a burst-based transmission, the ACK-clock scheduling
> with a self-managed timer and the RTT-based congestion control loop
> with an Ack-based Capacity and Congestion Estimation (ACCE) module. In
> non-technical words, it sends data down the stack when its internal
> timer expires, and the timing of the received ACKs contribute to
> updating this timer regularly.
>
> It is the first TCP congestion control that uses the timing constraint
> developed in the Linux kernel.
You seem to have missed BBR.
This is against what we have worked in the last years, preventing bursts
in the first place.
If this series is to address WIFI peculiarities with TSQ (this is a well
known problem, still waiting for a fix), I would rather not add all this
code in TCP and find better alternatives.
Since you do not provide information and testing results, there is no
chance we accept such patches.
Your work seems to be a variation of TSQ, and a very complex one.
Powered by blists - more mailing lists