From: Dave Taht <dave.taht@gmail.com>
To: Etienne Champetier <champetier.etienne@gmail.com>
Cc: cake@lists.bufferbloat.net,
Jonathan Morton <chromatix99@gmail.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] CAKE upstream in LEDE
Date: Tue, 7 Jun 2016 08:32:57 -0700 [thread overview]
Message-ID: <CAA93jw68Tbqyf8D=kdUbfMaB++Km0WT2Z9hL4oGUScGQJREz9g@mail.gmail.com> (raw)
In-Reply-To: <CAOdf3goH1PskYD_rdp=Mek3TdD8N5Btzkm2Vi_HBZngzhg38ww@mail.gmail.com>
On Tue, Jun 7, 2016 at 8:20 AM, Etienne Champetier
<champetier.etienne@gmail.com> wrote:
> Hi Dave,
>
> Le 7 juin 2016 5:01 PM, "Dave Taht" <dave.taht@gmail.com> a écrit :
>>
>> And it has already shown up for at least one of my main target platforms:
>>
>>
>> https://downloads.lede-project.org/snapshots/targets/mvebu/generic/packages/
>>
>> This will speed up my attempts to test at longer rtts (when I have
>> time) enormously. Thx for getting cake upstream to lede! I am tempted
>> to retire my last remaining cerowrt wndr3800, but the build has not
>> made it there (or to x86-64) as yet.
>>
>>
>> https://downloads.lede-project.org/snapshots/targets/ar71xx/generic/packages/
>>
>> As a side note, I am contributing a honking big (16 cpu) build box to
>> the lede effort from google's cloud. I wish I had a way to pay for it
>> (and additional ones) long term.
>
> Just curious, how much does this cost (and for what specs)?
I'll know in a month. (the lede folk got it doing builds may 27th)
It's a "16 VCPU N1-standard-16" instance. Estimate appears to be about
500/month.
The 4 cpu box that I am still contributing to the openwrt project runs
me about 250/month. I mentally have just taken what I get from
https://www.patreon.com/dtaht?ty=hy.
and sent it that way. I've had offers from various places to cover the
cost of the build system, but I have not got around to pursuing them
yet, I felt it was saner to help kickstart the lede effort any way I
could, first.
> Regards
> Etienne
>
>>
>> On Tue, Jun 7, 2016 at 7:19 AM, Jonathan Morton <chromatix99@gmail.com>
>> wrote:
>> >
>> >> On 7 Jun, 2016, at 12:53, Kevin Darbyshire-Bryant
>> >> <kevin@darbyshire-bryant.me.uk> wrote:
>> >>
>> >> For those interested, Jonathan Morton's CAKE qdisc has made it into
>> >> LEDE.
>> >
>> > Excellent. And thanks for taking care of the administrivia for me. :-)
>> >
>> > - Jonathan Morton
>> >
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-06-07 15:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 9:53 [Cake] " Kevin Darbyshire-Bryant
2016-06-07 14:19 ` Jonathan Morton
2016-06-07 15:01 ` [Cake] [Bloat] " Dave Taht
2016-06-07 15:20 ` Etienne Champetier
2016-06-07 15:32 ` Dave Taht [this message]
2016-06-07 15:57 ` Etienne Champetier
2016-06-08 20:41 ` Outback Dingo
2016-06-07 15:45 ` Dave Taht
2016-06-07 16:07 ` [Cake] " Dave Taht
2016-06-07 16:56 ` Kevin Darbyshire-Bryant
2016-06-07 17:00 ` Dave Taht
2016-06-07 17:04 ` Kevin Darbyshire-Bryant
2016-06-07 17:23 ` Dave Taht
2016-06-07 17:44 ` Kevin Darbyshire-Bryant
2016-06-07 18:48 ` moeller0
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='CAA93jw68Tbqyf8D=kdUbfMaB++Km0WT2Z9hL4oGUScGQJREz9g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=champetier.etienne@gmail.com \
--cc=chromatix99@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