Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake on LEDE - package maintainer required
Date: Tue, 13 Jun 2017 23:40:17 +0100	[thread overview]
Message-ID: <faebe5ea-a3f3-0714-24a9-a4f82f035ecd@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <20170613150244.695f2fd9@xeon-e3>

On 13/06/2017 23:02, Stephen Hemminger wrote:
> 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

Not sure if this is aimed at me specifically, however I shall give a
personal, from the heart and from my perspective, full of my opinion, reply.

> 
> I will keeping asking the questions.

They're good questions.

> If it works and has value, why is it not upstream?

It works and has value to me, specifically in the NAT aware per internal
host fairness on both ingress & egress.  It is not upstream because the
person who really understands how it works hasn't pushed it upstream.

If I were in that person's position, I know I'd not be looking forward
to the process of trying to do so, but then I'm somewhat 'burnt out'
from similar processes of trying to get some sensible improvements into
some user space code.

> If is not upstream, does it still matter?

To me, yes, because it's the only fair queueing AQM of which I'm aware
that'll have a go at per-IP fairness all in one easily configurable box.

KDB

  reply	other threads:[~2017-06-13 22:40 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 [this message]
2017-06-22  0:42   ` Dave Taht
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=faebe5ea-a3f3-0714-24a9-a4f82f035ecd@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    --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