From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] qos calculator & paper for htb rate selection
Date: Sat, 18 Jun 2016 17:53:43 -0700 [thread overview]
Message-ID: <CAA93jw5gcBbvib2eHu-+=vpgChm-NPcoRMJ=Pp_nqNDwq2yoSQ@mail.gmail.com> (raw)
I do keep hoping that one day we'll just be able to plug values into
an equation and come up with the right "thing".
Anyway, this paper had some pretty graphs and some severe flaws - like
only using long flows, not emulating longer RTTs, nor experimenting
with speeds greater than 40mbit. Some of the results, I think, hold,
but I'd have to think about it. I was attracted to reading it because
it attempted to take our "85%" rule for sqm-scripts on downloads and
attach some science to it...
http://sci-hub.bz/10.1109/TNET.2014.2366496
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next reply other threads:[~2016-06-19 0:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 0:53 Dave Taht [this message]
2016-06-19 3:43 ` Jonathan Morton
2016-06-19 4:20 ` Dave Taht
2016-06-19 18:37 ` moeller0
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='CAA93jw5gcBbvib2eHu-+=vpgChm-NPcoRMJ=Pp_nqNDwq2yoSQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@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