Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: moeller0 <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Benjamin Cronce <bcronce@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] [lede-project/source] Add support for cake qdisc (#72)
Date: Wed, 1 Jun 2016 17:19:09 +0200	[thread overview]
Message-ID: <A1890670-6362-42F5-BC93-5F7DB311CA1C@gmx.de> (raw)
In-Reply-To: <54AE2960-D312-479D-8411-96993F087EF7@gmail.com>

Hi Jonathan,

> On Jun 1, 2016, at 15:51 , Jonathan Morton <chromatix99@gmail.com> wrote:
> 
> 
>> On 1 Jun, 2016, at 15:25, Benjamin Cronce <bcronce@gmail.com> wrote:
>> 
>> 1) Ideally, regardless of platform, should an AQM or scheduler have the responsibility of changing anything other than ECN?
> 
> This was in part my original objection to having the squash/wash feature in Cake.
> 
> The other part is that if we are going to rewrite the rest of the TOS byte (not just the ECN bits), then we should do it properly, which requires a rather substantial extension to the configuration API, even if we only try to cover the most obvious use-cases.

	To play devils advocate here, re-mapping to zero might be a special case, but probably the single most important special case, so lack of generality is not the strongest argument against it (as long as the goal is “good enough”). But I already conceded, it is contentious so needs to go, cake is your “baby” so you have the honor to make such calls…

> 
> This would then be a “semi proprietary” DSCP configurator, acting independently of Cake’s core AQM and shaping functions, which would have to be duplicated in other AQMs which had similar aims to Cake.  That’s not a good thing, and feeds back into the first point.

	Not necessarily, one could also argue that the first implementation is free to just “do it” and only after it proofed itself useful one needs to think about generalizing it.

> 
> Hence the correct solution is to put DSCP rewriting elsewhere, making it reusable.
> 
> In Linux, doing ingress DSCP rewriting before it hits the ingress qdisc presently requires the rewriter itself to be a qdisc, but this can have Cake as a child qdisc.  For the simple “clearing” case iptables can be used instead, as long as Cake is configured to ignore the inbound DSCP using the “besteffort” flag.

	I seem to recall that iptables/nftables folks want to be able to “connect” to the ingress ssytem, so maybe that solves the whole issue (short of making the common thing (re-map to zero) simple)

All that said, the decision is made and cake is on its path to upstream somehow, whoooot.

Best Regards
        Sebastian

> 
> - Jonathan Morton
> 


  reply	other threads:[~2016-06-01 15:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lede-project/source/pull/72@github.com>
     [not found] ` <lede-project/source/pull/72/c222782884@github.com>
2016-06-01 10:02   ` Kevin Darbyshire-Bryant
2016-06-01 10:13     ` Dave Täht
2016-06-01 10:20       ` Kevin Darbyshire-Bryant
2016-06-01 10:52         ` moeller0
2016-06-01 11:20           ` Toke Høiland-Jørgensen
2016-06-01 11:41             ` moeller0
2016-06-01 11:47               ` Kevin Darbyshire-Bryant
2016-06-01 11:57                 ` Sebastian Moeller
2016-06-01 12:25                   ` Benjamin Cronce
2016-06-01 13:09                     ` Kevin Darbyshire-Bryant
2016-06-01 13:51                     ` Jonathan Morton
2016-06-01 15:19                       ` moeller0 [this message]
2016-06-01 20:22                         ` David Lang
2016-06-01 15:26                       ` Dave Taht

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=A1890670-6362-42F5-BC93-5F7DB311CA1C@gmx.de \
    --to=moeller0@gmx.de \
    --cc=bcronce@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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