From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] cake notes
Date: Sat, 27 Jun 2015 11:19:23 -0700 [thread overview]
Message-ID: <CAA93jw4tPaR=JwhvA3inpDxCQzKkzMagy7Z=wSqeB=001mriXA@mail.gmail.com> (raw)
I think exposing an "interval" param (at least) is needed for those
that want to try cake on satellite links.
still want squashing and ultimately diffserv intercon.
need testing with drr + cake and some filters (sort of an isp
environment) - I do not know if drr works right with stuff that can
drop packets.
the new flow hashing apis continue to settle upstream in 4.X with no
actual users in the code.
I have been misusing the bandwidth parameter to put a cap on memory use on wifi.
a stat shown on active flows would be good. There was some other stat
I wanted...
and getting more users to get more feedback would be good.
--
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
reply other threads:[~2015-06-27 18:19 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='CAA93jw4tPaR=JwhvA3inpDxCQzKkzMagy7Z=wSqeB=001mriXA@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