Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake/tc - removal of atm/ptm/ethernet specific overhead keywords
Date: Thu, 2 Jun 2016 17:22:03 +0300	[thread overview]
Message-ID: <2A84540D-AA30-4BD0-AF9A-5510EA00B7E8@gmail.com> (raw)
In-Reply-To: <574FFE52.1040501@darbyshire-bryant.me.uk>


> On 2 Jun, 2016, at 12:37, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> 
> I'd be sort of interested to know if anyone is actually using those keywords: ipoa-vcmux, ipoa-llcsnap, bridged-vcmux, bridged-llcsnap, ppoa-vcmux, pppoa-llc, pppoe-vcmux, pppoe-llcsnap, pppoe-ptm, bridged-ptm, via-ethernet, ether-phy, ether-all, ether-fcs, ether-vlan.
> 
> How many actually knew they even existed?

Since they are poorly documented, probably not many.  But I’d rather improve the documentation than delete them.

In principle, the existence and naming of these keywords is a potential clue to the uninitiated user of the overhead feature’s purpose.  The concept of protocol overhead affecting shader function is not an obvious one outside of networking specialists; making users look up a number in a cryptic table will simply result in nobody doing it at all.

Having shortcut keywords for this purpose in tc also helps to avoid the trap of other UI layers doing their own (incomplete or inaccurate) research on the correct compensation to apply.  Currently LuCI is extremely clumsy at handling SQM configuration, and the general quality of vendor firmware doesn’t give me confidence.

I’ve just pushed an update which makes all the keywords incremental, rather than some of them being absolute.  Existing correct examples of how to use these keywords remain correct.

It would be nice if LuCI could infer information about the likely overheads from the rest of the configuration, and apply (or suggest & default) the correct keywords in sqm-scripts.  That would make the feature much more widely used.

 - Jonathan Morton


  reply	other threads:[~2016-06-02 14:22 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 [this message]
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
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=2A84540D-AA30-4BD0-AF9A-5510EA00B7E8@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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