From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Dave Taht <dave@taht.net>, Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cake] [Cerowrt-devel] https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-06 is in last call
Date: Mon, 4 Feb 2019 02:40:37 -0800 [thread overview]
Message-ID: <CAA93jw6Hf=dVQirZabW7byPptAdeqZZxED0nxiW6SFshAE09CQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1902041132530.23912@uplift.swm.pp.se>
On Mon, Feb 4, 2019 at 2:34 AM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> On Mon, 4 Feb 2019, Dave Taht wrote:
>
> >> The problem with CAKE/FQ and background traffic is that it can't tell if
> >> there is congestion or not, and things like LEDBAT can't backoff and try
> >> to avoid causing congestion. So your previous email about allowing some
> >> congestion to take place on LE would be good as then protocols that try to
> >> avoid causing congestion would have a way to do so.
> >
> > I do not like that the standard allows for total starvation. I would
> > prefer it had a minimum of 5%.
>
> I fully agree, and that would work even if all LE traffic was put into
> single queue with 5% of total bw, and even if that had a 1 second FIFO
> with tail drop.
We don't quite agree.
"Every application has the right to one packet in the network" - John Nagle
Cake adheres to that as closely as possible, yet still keeps latency
low for all applications background, priority or best effort. fq_codel
doesn't, which leads to shorter queue lengths when ECN is in heavy
use. I wish cake would more aggressively drop ECN packets.
Sadly cake's uptake is a bit slow, as it is a bit slow.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next prev parent reply other threads:[~2019-02-04 10:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 18:39 [Cake] " Dave Taht
2019-02-03 20:02 ` [Cake] [Cerowrt-devel] " Jonathan Morton
2019-02-03 22:42 ` David P. Reed
2019-02-04 0:17 ` Dave Taht
2019-02-04 1:12 ` Jonathan Morton
2019-02-04 6:02 ` Mikael Abrahamsson
2019-02-04 6:58 ` Dave Taht
2019-02-04 7:11 ` Mikael Abrahamsson
2019-02-04 10:23 ` Dave Taht
2019-02-04 10:34 ` Mikael Abrahamsson
2019-02-04 10:40 ` Dave Taht [this message]
2019-08-21 15:07 ` [Cake] " Dave Taht
2019-08-21 16:38 ` Kevin Darbyshire-Bryant
2019-08-21 16:52 ` [Cake] [Cerowrt-devel] " Dave Taht
2019-08-22 6:11 ` Mikael Abrahamsson
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='CAA93jw6Hf=dVQirZabW7byPptAdeqZZxED0nxiW6SFshAE09CQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=swmike@swm.pp.se \
/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