From: Benjamin Cronce <bcronce@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake over satellite
Date: Tue, 20 Oct 2015 20:26:13 -0500 [thread overview]
Message-ID: <CAJ_ENFH54n0Aj_rao3+oAXaSPzLYS2nCrGi80ZerRcgJ2qyXsQ@mail.gmail.com> (raw)
In-Reply-To: <56267AB6.6080604@darbyshire-bryant.me.uk>
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
Because planet very way too much and even a given planet will have a wide
range of much greater than one our RTTs. TCP probably won't even work for
those kids of RTTs. What about a Lunar RTT instead of Interplanetary? The
moon is about 1.3 light seconds away, one way. That's a minimum of 2.6sec
RTT.
On Tue, Oct 20, 2015 at 12:32 PM, 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.
>
> Kevin
>
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
>
[-- Attachment #2: Type: text/html, Size: 3087 bytes --]
next prev parent reply other threads:[~2015-10-21 1:26 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 [this message]
2015-10-21 1:31 ` Jonathan Morton
2015-10-23 7:58 ` Sebastian Moeller
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=CAJ_ENFH54n0Aj_rao3+oAXaSPzLYS2nCrGi80ZerRcgJ2qyXsQ@mail.gmail.com \
--to=bcronce@gmail.com \
--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