From: Dave Taht <dave.taht@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Help with the AQM layer
Date: Mon, 12 Oct 2015 10:18:09 +0200 [thread overview]
Message-ID: <CAA93jw4w+PNB9uC6RU_RHsmaAPgbht7DOVEH8GorwHCyBy4zWA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6urHN1fjuTcYGzMeg4QcuVq3AHmEHg4R=p1_cRmtUqEQ@mail.gmail.com>
so, awesome, merge it.
On Mon, Oct 12, 2015 at 10:17 AM, Dave Taht <dave.taht@gmail.com> wrote:
> no, I missed your branch and announcement entirely.
>
> On Mon, Oct 12, 2015 at 10:12 AM, Kevin Darbyshire-Bryant
> <kevin@darbyshire-bryant.me.uk> wrote:
>> Hi Logan,
>>
>> On 08/10/15 I pushed an 'exposeinterval' feature branch to both mine &
>> dave's sch_cake & tc-adv repos (so module & user side changes) which
>> exposed the interval (rtt) parameter. By the following morning it even
>> worked! On Morning of 11th Dave sent an email "adding 'rtt' support
>> correctly" to which I rather assumed my 'exposeinterval' branch was
>> superfluous, incorrect and unneeded so I removed them from Dave's repos
>> in the expectation of great things.
>>
>> You'll still find my original versions of that branch
>> https://github.com/kdarbyshirebryant/sch_cake/tree/exposeinterval &
>> https://github.com/kdarbyshirebryant/tc-adv/tree/exposeinterval
>>
>> A glance over Dave's patch suggests the only difference to the
>> 'rtt/interval' side of things between his & mine is using nanoseconds in
>> the pass from user-space to kernel space rather than my use of milliseconds.
>>
>> If you provide tc with a 'rtt 300ms' parameter it should work a treat.
>>
>> Kevin
>>
>>
>> On 12/10/15 08:47, Loganaden Velvindron wrote:
>>> Hi folks,
>>>
>>> I'm reading about this on the website:
>>>
>>> "
>>> The AQM layer has no configuration options. However, it is planned to
>>> add simple tuning options for different prevailing RTTs that may be
>>> significantly different from the Internet-scale 100ms currently
>>> assumed. Satellite links tend to impose longer RTTs, and enclosed LANs
>>> tend to have much shorter RTTs.
>>> "
>>>
>>> In Mauritius, and other african countries, we have RTT of around
>>> 300-400 ms. Could someone please point me to where I should look for
>>> adding a tunable for this in the source files ?
>>>
>>>
>>> Kind regards,
>>> //Logan
>>> C-x-C-c
>>>
>>>
>>> _______________________________________________
>>> Cake mailing list
>>> Cake@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cake
>>
>>
>>
>> _______________________________________________
>> Cake mailing list
>> Cake@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cake
>>
>
>
>
> --
> Dave Täht
> Do you want faster, better, wifi? https://www.patreon.com/dtaht
--
Dave Täht
Do you want faster, better, wifi? https://www.patreon.com/dtaht
next prev parent reply other threads:[~2015-10-12 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 7:47 Loganaden Velvindron
2015-10-12 7:51 ` Dave Taht
2015-10-12 8:12 ` Kevin Darbyshire-Bryant
2015-10-12 8:17 ` Dave Taht
2015-10-12 8:18 ` Dave Taht [this message]
2015-10-12 8:46 ` Kevin Darbyshire-Bryant
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=CAA93jw4w+PNB9uC6RU_RHsmaAPgbht7DOVEH8GorwHCyBy4zWA@mail.gmail.com \
--to=dave.taht@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