From: Dave Taht <dave.taht@gmail.com>
To: Daniel Havey <dhavey@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
cake@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] active sensing queue management
Date: Wed, 10 Jun 2015 12:53:20 -0700 [thread overview]
Message-ID: <CAA93jw4TSXDEe8Y0VCRQvS5xKU6sM4t5or962iv079-FcCEMNQ@mail.gmail.com> (raw)
http://dl.ifip.org/db/conf/networking/networking2015/1570064417.pdf
gargoyle's qos system follows a similar approach, using htb + sfq, and
a short ttl udp flow.
Doing this sort of measured, then floating the rate control with
"cake" would be fairly easy (although it tends to be a bit more
compute intensive not being on a fast path)
What is sort of missing here is trying to figure out which side of the
bottleneck is the bottleneck (up or down).
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next reply other threads:[~2015-06-10 19:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 19:53 Dave Taht [this message]
2015-06-10 20:54 ` [Cerowrt-devel] [Cake] " Sebastian Moeller
2015-06-11 0:10 ` Daniel Havey
2015-06-11 7:27 ` Sebastian Moeller
2015-06-12 15:02 ` Daniel Havey
2015-06-12 16:02 ` Sebastian Moeller
2015-06-12 1:49 ` David Lang
2015-06-12 14:44 ` Daniel Havey
2015-06-13 4:00 ` David Lang
2015-06-13 5:50 ` Benjamin Cronce
2015-06-11 1:05 ` Alan Jenkins
2015-06-11 7:58 ` Sebastian Moeller
2015-06-12 1:44 ` [Cerowrt-devel] [Bloat] " David Lang
2015-06-12 9:52 ` MUSCARIELLO Luca IMT/OLN
2015-06-12 16:51 ` Benjamin Cronce
2015-06-13 4:16 ` David Lang
2015-06-12 12:18 ` Sebastian Moeller
2015-06-12 13:00 ` Alan Jenkins
2015-06-12 14:35 ` Daniel Havey
2015-06-12 17:55 ` Alan Jenkins
2015-06-13 4:34 ` David Lang
2015-06-13 4:30 ` David Lang
2015-06-13 5:37 ` [Cerowrt-devel] [Cake] [Bloat] " Benjamin Cronce
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4TSXDEe8Y0VCRQvS5xKU6sM4t5or962iv079-FcCEMNQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dhavey@gmail.com \
/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