From: Sebastian Moeller <moeller0@gmx.de>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake over satellite
Date: Fri, 23 Oct 2015 09:58:58 +0200 [thread overview]
Message-ID: <A9379832-0EFE-42CD-A10F-5A83D86B9F4A@gmx.de> (raw)
In-Reply-To: <56267AB6.6080604@darbyshire-bryant.me.uk>
Hi Kevin,
On Oct 20, 2015, at 19:32 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> On 19/10/15 20:05, Sebastian Moeller wrote:
>> Hi,
>>
>> On October 19, 2015 10:24:01 AM CDT, Dave Taht <dave.taht@gmail.com> wrote:
>>> well, yes, but we can do it in the lab *this week*, before he takes
>>> the dingos on....
>> Good idea, als I am at A conference right now and will not find the time to make the changes to TC in time. I believe that cake should certainly A) set A reasonable target by default and B) still allow the user to explicitly request something else. Currently, I believe cake does only A)...
>>
>> Besteht Regards
>> Sebadtian
>>
>>
>
> As an FYI:
>
>
> tc has a number of calculations for interval & target
>
> If an rtt is specified then target is 5% of interval with 1uS
> (microsecond!) and 5mS (millisecond) lower & upper bounds.
>
> The keyword predefined rtt values are:
>
> datacentre (100uS), lan (1mS), metro(10mS), regional(30mS),
> internet(100mS), oceanic(300mS), satellite(1000mS), interplanetary(1hour!)
> Corresponding targets are 5uS, 50uS, 500uS, 1.5mS and everything from
> internet onwards as a 5mS target.
>
> Although these are the values passed into cake from tc, that isn't the
> final story with regard to calculations as cake qdisc has some further
> sanity checks.
>
> If a link bandwidth is specified then the target is set to the max of
> '1.5 MTU's worth of link time' and the target value passed by tc. The
> interval is set to max of '8 times the calculated target' and interval
> value passed by tc.
>
> So whilst tc supplies an rtt/interval and a 5% calculated target, cake
> itself will override this with sensible values if that makes sense for a
> 'slow' link.
Thanks for elucidating this. I believe that cake should honor silly requests by the user as long as those were stated explicitly by the users and are possible (so target <= interval). It is great that cake has sane defaults and I also believe it would be helpful if cake noticed the user of unusual parameter configuration, but in the end the user should be able to control the parameters. (I am fine with having a —override_sane_cake_defaults command line switch to make it hard to do silly things accidentally). “Do the right thing by default, but allow unreasonable configurations if asked nicely” should be the goal here, I believe (but I admit Jonathan’s project, and hence his call)
Best Regards
Sebastian
>
> Kevin
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2015-10-23 7:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 14:55 Noven Purnell-Webb
2015-10-19 14:58 ` Dave Taht
2015-10-19 14:59 ` Loganaden Velvindron
2015-10-19 15:15 ` Sebastian Moeller
2015-10-19 15:24 ` Dave Taht
2015-10-19 19:05 ` Sebastian Moeller
2015-10-20 17:32 ` Kevin Darbyshire-Bryant
2015-10-21 1:26 ` Benjamin Cronce
2015-10-21 1:31 ` Jonathan Morton
2015-10-23 7:58 ` Sebastian Moeller [this message]
2015-10-19 15:48 ` Kevin Darbyshire-Bryant
2015-10-19 19:58 ` Sebastian Moeller
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=A9379832-0EFE-42CD-A10F-5A83D86B9F4A@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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