Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake on LEDE - package maintainer required
Date: Wed, 21 Jun 2017 17:42:20 -0700	[thread overview]
Message-ID: <87r2ycc0pf.fsf@nemesis.taht.net> (raw)
In-Reply-To: <20170613150244.695f2fd9@xeon-e3> (Stephen Hemminger's message of "Tue, 13 Jun 2017 15:02:44 -0700")


I have long sought sufficient funding to push cake into the mainstream
and come up empty. Cake represents thousands of hours of volunteer labor
as it is, and everyone that has worked on it deserves kudos...

... and a check...

or at least... a bloody t-shirt. And I mean that both in the perjorative
sense and in the descriptive sense, of being covered in scars.

Honestly, I'd settle for some happy set of users of cake to throw in for
the t-shirt, at the very least.

Stephen Hemminger <stephen@networkplumber.org> writes:

> On Tue, 13 Jun 2017 18:41:05 +0100
> Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
>> Hi All,
>> 
>> This email finds me looking for a volunteer/s to take over the ownership 
>> of the cake qdisc module package in LEDE.
>> 
>> It's not particularly onerous, in essence making sure the package points 
>> at the git commit considered 'stable'.
>> 
>> In theory there's a 'matching' user space patch for 'tc' in the 
>> 'iproute2' package to ensure it agrees with the kernel space qdisc.
>> 
>> My advice is for everyone to take a step back very quickly...as the last 
>> person left forward of the line will get it ;-)
>> 
>> Cheers,
>> 
>> Kevin
>
> I will keeping asking the questions.
> If it works and has value, why is it not upstream?
> If is not upstream, does it still matter?

It's pretty much the default for me 'round here. It solved all the
remaing problems the sqm-scripts had. 

> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake

  parent reply	other threads:[~2017-06-22  0:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 17:41 Kevin Darbyshire-Bryant
2017-06-13 22:02 ` Stephen Hemminger
2017-06-13 22:40   ` Kevin Darbyshire-Bryant
2017-06-22  0:42   ` Dave Taht [this message]
2017-06-27 22:11     ` Stephen Hemminger
2017-06-27 23:58 ` Outback Dingo
2017-06-28  8:02   ` Kevin Darbyshire-Bryant
     [not found] <mailman.3.1498147201.32609.cake@lists.bufferbloat.net>
2017-06-25  4:51 ` Georgios Amanakis

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=87r2ycc0pf.fsf@nemesis.taht.net \
    --to=dave@taht.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    --cc=stephen@networkplumber.org \
    /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