On Wed, 29 Nov 2017 10:41:41 -0800 Dave Taht <dave.t...@gmail.com> wrote:
> On Wed, Nov 29, 2017 at 10:21 AM, Juliusz Chroboczek <j...@irif.fr> wrote: > >> The better solution would of course be to have the TCP peeps change the > >> way TCP works so that it sends fewer ACKs. > > > > Which tends to perturb the way the TCP self-clocking feedback loop works, > > and to break Nagle. > > Linux TCP is no longer particularly ack-clocked. In the post pacing, > post sch_fq world, packets are released (currently) on a 1ms schedule. > Support was recently released for modifying that schedule on a per > driver basis, which turns out to be helpful for wifi. > > see: https://www.spinics.net/lists/netdev/msg466312.html Also TCP BBR has lost its initial luster since it is unfair and ignores losses and ECN (see recent netdev paper). _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat
