Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Nils Andreas Svee <nils@stokkdalen.no>
Cc: Dave Taht <dave@taht.net>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake upstream Planning
Date: Wed, 15 Nov 2017 21:58:32 +0100	[thread overview]
Message-ID: <246DB6BC-8045-47F6-8719-8CBDE3E776AD@gmail.com> (raw)
In-Reply-To: <1510777703.2726870.1173824208.148E1D2D@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]


> On Nov 15, 2017, at 9:28 PM, Nils Andreas Svee <nils@stokkdalen.no> wrote:
> 
> On Wed, Nov 15, 2017, at 21:19, Dave Taht wrote:
>> 
>>> There’s also been a Cake support feature request hanging around in the EdgeOS
>>> forums for a while after Lochnair’s successful work to get it built for the
>>> EdgeRouter firmware:
>>> 
>>> https://community.ubnt.com/t5/EdgeMAX-Feature-Requests/Cake-shaper-support/idi-p/1885749
>> 
>> I had viewed those folk as a key path to commercialization. They have
>> a great user community and great products.
>> 
>>> Maybe this would help get it pushed through into a device that I think has
>>> pretty wide deployment…
>> 
>> The problem is, they were stuck on kernel 3.10, when last I looked and
>> oy...
>> 
>> I keep hoping we can get cavium to pay attention directly.
> Sadly they're still stuck 3.10. The next FW will be based on the
> 3.10.107 kernel, instead of 3.10.14/3.10.20. So that's something, but
> it's still ancient and EOL.

Is the tie to 3.10 due to the dependency on the Cavium SDK for hardware support?

Surprisingly I don’t see a feature request so far for a newer kernel, at least among the first half dozen pages or so:

https://community.ubnt.com/t5/EdgeMAX-Feature-Requests/idb-p/EdgeMAX_Ideas/tab/most-kudoed <https://community.ubnt.com/t5/EdgeMAX-Feature-Requests/idb-p/EdgeMAX_Ideas/tab/most-kudoed>


[-- Attachment #2: Type: text/html, Size: 2421 bytes --]

  reply	other threads:[~2017-11-15 20:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7.1510506001.13084.cake@lists.bufferbloat.net>
2017-11-14  9:51 ` [Cake] Donation Pete Heist
2017-11-14 20:10   ` Dave Taht
2017-11-15 14:41     ` Pete Heist
2017-11-15 19:44       ` [Cake] Cake upstream Planning Dave Taht
2017-11-15 20:04         ` Dave Taht
2017-11-15 20:44           ` Pete Heist
2017-11-15 20:49             ` Dave Taht
2017-11-15 20:06         ` Pete Heist
2017-11-15 20:19           ` Dave Taht
2017-11-15 20:28             ` Nils Andreas Svee
2017-11-15 20:58               ` Pete Heist [this message]
2017-11-15 22:40                 ` Nils Andreas Svee
2017-11-16  8:41                   ` Pete Heist
     [not found] <mailman.1019.1510802012.3609.cake@lists.bufferbloat.net>
2017-11-16  9:14 ` Pete Heist
2017-11-16 16:31   ` Dave Taht
2017-11-16 18:40     ` Pete Heist
2017-11-16 19:13       ` Dave Taht
     [not found] <mailman.1013.1510778675.3609.cake@lists.bufferbloat.net>
2017-11-16  9:50 ` Pete Heist

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=246DB6BC-8045-47F6-8719-8CBDE3E776AD@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --cc=nils@stokkdalen.no \
    /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