Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: Pete Heist <peteheist@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake upstream Planning
Date: Wed, 15 Nov 2017 12:19:43 -0800	[thread overview]
Message-ID: <87lgj75m74.fsf@nemesis.taht.net> (raw)
In-Reply-To: <CC245853-163F-4740-9026-26238B69B8C8@gmail.com> (Pete Heist's message of "Wed, 15 Nov 2017 21:06:53 +0100")


Pete Heist <peteheist@gmail.com> writes:

>     On Nov 15, 2017, at 8:44 PM, Dave Taht <dave@taht.net> wrote:
>
>     
>     
>     I dearly would like to try and submit cake to mainline linux in
>     december. Getting it done is going to take group effort.
>     
>     And trying to cover all the corner cases, is going to take co-ordination
>     and scripting, and perhaps we should switch to google docs to pull together.
>     
>     Also, it might be fun to schedule a dramatic reading of the source code
>     via videoconference because theres a lot in cake that not enough people
>     (except maybe jonathan) understand.
>     
>
> That sounds good. Rather than my making some test plan, if you start a doc just
> plug me in where you think it’s best.

I'll try to review what's been discussed so far and get a document out
by sunday.

BTW, all, I have reserved time on the "vuc" conference december 15th to
discuss where we are in the bufferbloat project. That's more of a "meet
the press" kind of thing than the internal discussion here.

>
> 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.

  reply	other threads:[~2017-11-15 20:19 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 [this message]
2017-11-15 20:28             ` Nils Andreas Svee
2017-11-15 20:58               ` Pete Heist
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=87lgj75m74.fsf@nemesis.taht.net \
    --to=dave@taht.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=peteheist@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