From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dash traffic "chunklets" verses pie and fq_codel
Date: Fri, 8 Sep 2017 09:32:15 +0200 [thread overview]
Message-ID: <20170908073215.dba5utrwuwvruw55@sesse.net> (raw)
In-Reply-To: <CAA93jw7Rwrbv1em9zJvFoFPSfPiNWoc4sdOHL==xZUDNiujNVA@mail.gmail.com>
On Thu, Sep 07, 2017 at 04:52:54PM -0700, Dave Taht wrote:
> good read:
>
> http://caia.swin.edu.au/cv/jkua/preprint/jkua-icccn2017-chunklets-preprint-10may17.pdf
Aaaaa!
“For example, FQ-CoDel isolates individual traffic flows into
sub-queues then serves each sub-queue with a Deficit Round
Robin (DRR) scheduler. The result is relatively even capacity
sharing, which may actually be detrimental to a DASH flow
(often a single, persistent TCP connection) that is competing
with multiple other concurrent TCP flows.”
Isn't this just an AQM sabotage scheme?
/* Steinar */
--
Homepage: https://www.sesse.net/
next prev parent reply other threads:[~2017-09-08 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 23:52 Dave Taht
2017-09-08 7:32 ` Steinar H. Gunderson [this message]
2017-09-08 11:50 ` Jonathan Morton
2017-09-08 18:14 ` Dave Taht
2017-09-08 17:51 ` 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170908073215.dba5utrwuwvruw55@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=bloat@lists.bufferbloat.net \
/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