Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>, cake@lists.bufferbloat.net
Subject: Re: [Cake] cake/tc - removal of atm/ptm/ethernet specific overhead keywords
Date: Thu, 2 Jun 2016 20:40:06 +0300	[thread overview]
Message-ID: <D88BC3DB-AE48-4892-B357-C197AFFBE3C8@gmail.com> (raw)
In-Reply-To: <6F215C7B-D4B2-484B-B728-61E0B83FF30E@gmx.de>


> On 2 Jun, 2016, at 18:42, moeller0 <moeller0@gmx.de> wrote:
> 
> I stopped believing this is “simple” a long time ago; I also failed to come up with a method to measure the actual overhead on VDSL links…

If it’s impossible to measure, then by definition it doesn’t have a significant performance impact, and thus it doesn’t matter if it is sloppily estimated.  In that context an overestimate of overhead is safe.

This is really a user-interface problem.  I think it would be very helpful for LuCI to get a basic, easy “conservative overhead compensation” button that simply turns on the “conservative” keyword for both ingress and egress.  That’s the bare minimum.

We can discuss details of improving granularity of that setting at greater leisure, preferably in the context of a proper redesign of the SQN configuration.

And let’s be absolutely clear: I will NOT drop the shortcut keywords from tc.

 - Jonathan Morton


  reply	other threads:[~2016-06-02 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02  9:37 Kevin Darbyshire-Bryant
2016-06-02 14:22 ` Jonathan Morton
2016-06-02 14:27   ` Toke Høiland-Jørgensen
2016-06-02 14:49     ` Jonathan Morton
2016-06-02 15:42       ` moeller0
2016-06-02 17:40         ` Jonathan Morton [this message]
2016-06-02 18:53           ` moeller0
2016-06-02 18:55             ` Jonathan Morton
2016-06-02 19:17               ` moeller0
2016-06-02 14:59     ` moeller0
2016-06-02 15:10       ` Jonathan Morton
2016-06-02 15:33         ` moeller0
2016-06-02 14:51   ` moeller0

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=D88BC3DB-AE48-4892-B357-C197AFFBE3C8@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=toke@toke.dk \
    /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