Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	 bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] cake: changing bandwidth on the rate limiter dynamically
Date: Fri, 12 Dec 2014 07:52:28 -0800	[thread overview]
Message-ID: <CAA93jw7EmmdV8q4c+G6oBxfkgOhce++UVneDwsFc1pTd2gOvTg@mail.gmail.com> (raw)

One of the nice things that the gargoyle-qos system does is that it
attempts to measure the bandwidth actively and modify the actual
bandwidth in the rate limiter to suit.

It does this with some very hairy code into the htb/hfsc subsystem,
and measuring ping to either a server elsewhere or short ttl udp +
icmp returns.... (can't remember which)

dealing with the measurements correctly when traffic is possibly
bottlenecking in both directions I think it fails on. As does
streamboost.

Now, it turns out that cake makes altering the bandwidth really easy,
you can just change it from the command line.

http://pastebin.com/Jr9s6EBW

I am pretty sure changing it is currently pretty damaging to stuff in
flight (don't remember), but
it needent be.

I think dynamically sensing the underlying bandwidth would be a great
boon, rather than having to set it so explicitly, and perhaps by
sensing some other parameters like ack clocks or overall traffic flow
at a depth that bpf could resolve, might be a valid approach.


-- 
Dave Täht

http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

             reply	other threads:[~2014-12-12 15:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 15:52 Dave Taht [this message]
2014-12-12 15:59 ` Jonathan Morton
2014-12-12 17:44   ` Dave Taht
2014-12-13  2:55     ` Jonathan Morton
2014-12-13  3:57       ` Dave Taht
2014-12-14  8:30         ` Jonathan Morton

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=CAA93jw7EmmdV8q4c+G6oBxfkgOhce++UVneDwsFc1pTd2gOvTg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --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