From: Dave Taht <dave.taht@gmail.com>
To: Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: cake@lists.bufferbloat.net,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] openwrt build available with latest cake and fq_pie
Date: Sun, 14 Jun 2015 09:09:28 -0700 [thread overview]
Message-ID: <CAA93jw4XzLhudtQ=1+L6csv66d_sNgF6VLg8iqMZmPJHyc5ryw@mail.gmail.com> (raw)
In-Reply-To: <CANmMgnGY1qkm9PnfKmHMoB6OYzhD5Cr9WDPPjmG1Tenw=+4E-g@mail.gmail.com>
On Sun, Jun 14, 2015 at 8:53 AM, Alan Jenkins
<alan.christopher.jenkins@gmail.com> wrote:
> On 13/06/2015, Dave Taht <dave.taht@gmail.com> wrote:
>> Hopefully, by creating a "tc-adv" package (now in ceropackages) we are
>> nearly at the last step for being able to do builds out of the main
>> openwrt tree. I am puzzled as to how to correctly override the default
>> "tc" package, but at least this built and worked for me the first
>> time.
>>
>> so you can kill any local mods to the iproute2 package in your own
>> openwrt builds, and merely add tc-adv to your own build instead, and
>> build kmod-sched-fq_pie and kmod-sched-cake, and walla!
>>
>> assuming this is now correct, the next step would be to push tc-adv
>> into some mainline openwrt repo (routing?) and get it and the kmod-*
>> stuff built regularly out of their build system. (and then! yea! try
>> some faster boxes like the linksys ac1900 and see what new breaks!)
>>
>> Anyway, my barely tested latest build (cake works, at least) is at here:
>>
>> http://snapon.lab.bufferbloat.net/~cero3/lupin/ar71xx/
>>
>> This also includes the latest cake, although I disagree with jonathon
>> about the count/2 mod, might as well test.
I do pretty strongly think count - 1 is the rightest thing still. I
did come up with two
other ideas for the resumption phase that might work.
1) schedule the next drop based on count, THEN do a count - 2 or
count/2 to be scheduled for the drop phase afterwards
2) measure the amount of time since the last entrance to the
resumption phase and resume with count at some level slightly above
that.
probably even more useful than just hacking around:
A) measure all the time spent in all the phases relative to the
induced workloads.
we had code like that in the original versions of codel.
> New build still works for my link :). (15/1M dsl in the UK).
>
> If I want to test cake continuously, I'll need to fix sqm-scripts to
> pass the cake ATM options. I switched back to fq_codel for now (that
> worked as well).
Patches gladly accepted (tc-adv now does parse the new keywords I
think), and we really, really, really do need to confirm that the atm
code works in every circumstance.
> Alan
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next prev parent reply other threads:[~2015-06-14 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 22:58 [Cerowrt-devel] " Dave Taht
2015-06-14 15:53 ` [Cerowrt-devel] [Cake] " Alan Jenkins
2015-06-14 16:09 ` Dave Taht [this message]
2015-06-14 17:19 ` Jonathan Morton
2015-06-14 17:27 ` Toke Høiland-Jørgensen
2015-06-14 17:38 ` Dave Taht
2015-06-14 18:07 ` Jonathan Morton
2015-06-14 18:24 ` Dave Taht
2015-06-14 19:35 ` Jonathan Morton
2015-06-14 19:42 ` Dave Taht
2015-06-14 19:32 ` Alan Jenkins
2015-06-14 19:47 ` Sebastian Moeller
2015-06-14 20:43 ` Alan Jenkins
2015-06-14 20:54 ` 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/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='CAA93jw4XzLhudtQ=1+L6csv66d_sNgF6VLg8iqMZmPJHyc5ryw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=alan.christopher.jenkins@gmail.com \
--cc=cake@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