Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	cake@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat]  CAKE upstream in LEDE
Date: Tue, 7 Jun 2016 08:45:23 -0700	[thread overview]
Message-ID: <CAA93jw7VSJtP=hub70T3Soe3jKweeiwc2KTama3HrLbCOD8NTw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5usE8tYwX+dvM65B36D_7zWMhkBfQUoK1YzHz9Xm4W5A@mail.gmail.com>

On Tue, Jun 7, 2016 at 8:01 AM, Dave Taht <dave.taht@gmail.com> wrote:
> 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/

It looks like builds for this are now available, also. It looks to be
competitive with the omnia in most respects.

https://www.solid-run.com/marvell-armada-family/clearfog/

The turrus omnia appears to have been pushed back to october.

I do keep hoping someone will get BQL working right on the ethernet
drivers for these armada chips....

> 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.
>
> 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
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org



-- 
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org

  parent reply	other threads:[~2016-06-07 15:45 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
2016-06-07 15:57         ` Etienne Champetier
2016-06-08 20:41           ` Outback Dingo
2016-06-07 15:45     ` Dave Taht [this message]
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='CAA93jw7VSJtP=hub70T3Soe3jKweeiwc2KTama3HrLbCOD8NTw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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