Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake integration woes
Date: Fri, 1 May 2015 10:42:39 +0300	[thread overview]
Message-ID: <AB2145E1-80D7-4DB0-99AD-B9CBCE8C2F7C@gmail.com> (raw)
In-Reply-To: <CAA93jw7P-bANy3EJshofW4bBvqW+qg+kERs3iYWFTJNpEEOa1A@mail.gmail.com>


> On 30 Apr, 2015, at 19:25, Dave Taht <dave.taht@gmail.com> wrote:
> 
> 3) I really want that squash option.

And I really don’t think it belongs in cake.  Not unless we put a complete DSCP re-marking system in there, which would massively complicate the configuration interface, which we don’t want to do.

Let me emphasise: cake can already *ignore* DSCP.  So can anything else in a network, with the possible exception of stupid wifi interfaces, which in the long run we should try to fix.  If you’re using Diffserv internally, then you already have a re-marking system separate from cake, which can do the squashing for you.

And, on a more technical note, adding squashing means cake crosses a threshold - from not modifying packets (except for ECN marking, which has a special function for the job) to doing so.  I’d rather have a separate, specialised qdisc for the re-marking task, and put squashing in there instead.

> 4) I don't like the precedence option being in there at all.

This is perhaps fairer comment, since I don’t expect many people will use it.  But since it’s already in there, and isn’t very much code, it might not make sense to remove it.

 - Jonathan Morton


      parent reply	other threads:[~2015-05-01  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 16:25 Dave Taht
2015-04-30 22:42 ` Jonathan Morton
2015-05-01  7:42 ` Jonathan Morton [this message]

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=AB2145E1-80D7-4DB0-99AD-B9CBCE8C2F7C@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@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