From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] measuring "active flows"
Date: Fri, 8 Apr 2016 10:09:30 -0700 [thread overview]
Message-ID: <CAA93jw6SZKdHyurOEo1MO7827rxh+v8WBP4sTwQDOZ4LMxqJrQ@mail.gmail.com> (raw)
One of the nifty things about cake is that we are in a position to get
more of a grip on "active" flows with lots of contention. I have done
a bit of this ad-hoc here and there, with 100s of flows, the number
"active" (with a queue) at any given RTT are much less (at least with
drop rather than ecn)
https://www.researchgate.net/profile/S_Oueslati/publication/234778751_Evaluating_the_number_of_active_flows_in_a_scheduler_realizing_fair_statistical_bandwidth_sharing/links/5451fab10cf2bf864cbab666.pdf
(If you can't tell, I'm gradually trying to collect papers that were
influential on me)
Pretty much everything else luca and jim roberts has written is pure gold, too.
https://scholar.google.com/citations?user=Q36qUAsAAAAJ&hl=en
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
reply other threads:[~2016-04-08 17:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw6SZKdHyurOEo1MO7827rxh+v8WBP4sTwQDOZ4LMxqJrQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@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