Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>,
	Cake List <cake@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] benefits of ack filtering
Date: Wed, 29 Nov 2017 15:59:17 -0800	[thread overview]
Message-ID: <20171129155917.63d51add@xeon-e3> (raw)
In-Reply-To: <CAA93jw6ZBeCoTGwkS6e6+4TMOTM7YmQFYoMSxSBjTjn8e3gQqw@mail.gmail.com>

On Wed, 29 Nov 2017 10:41:41 -0800
Dave Taht <dave.taht@gmail.com> wrote:

> On Wed, Nov 29, 2017 at 10:21 AM, Juliusz Chroboczek <jch@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).


  parent reply	other threads:[~2017-11-29 23:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw47ZAXAJmiOVCb2NR3JRcCfmX0TLr+55O0G+J6HCW5bVQ@mail.gmail.com>
     [not found] ` <alpine.DEB.2.20.1711290655590.32099@uplift.swm.pp.se>
     [not found]   ` <7i1skhrln1.wl-jch@irif.fr>
2017-11-29 18:41     ` Dave Taht
2017-11-29 23:29       ` Steinar H. Gunderson
2017-11-29 23:59       ` Stephen Hemminger [this message]
2017-11-30  0:21         ` Eric Dumazet
     [not found] ` <7izi75q6rj.wl-jch@irif.fr>
2017-11-29 18:48   ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171129155917.63d51add@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jch@irif.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox