Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat-devel <bloat-devel@lists.bufferbloat.net>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cake: changing bandwidth on the rate limiter dynamically
Date: Fri, 12 Dec 2014 17:59:45 +0200	[thread overview]
Message-ID: <EA2119E5-63C8-472C-A241-65EB7F2FF879@gmail.com> (raw)
In-Reply-To: <CAA93jw7EmmdV8q4c+G6oBxfkgOhce++UVneDwsFc1pTd2gOvTg@mail.gmail.com>

> On 12 Dec, 2014, at 17:52, Dave Taht <dave.taht@gmail.com> wrote:
> 
> 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 don’t think it is harmful.  All that happens is that the packet issue deadlines start to be advanced at a different rate with each packet transmitted.  A change in the rate by that mechanism doesn’t cause any packet flushing or other trouble.

The flow-discrimination mode and the diffserv mode can also be changed in the same way, but this is more disruptive; it may at least result in some packets arriving out of order within flows, if not also some spurious drops.  But the network can tolerate that happening occasionally.

 - Jonathan Morton


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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 15:52 Dave Taht
2014-12-12 15:59 ` Jonathan Morton [this message]
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=EA2119E5-63C8-472C-A241-65EB7F2FF879@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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