From: Jonathan Morton <chromatix99@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
cake@lists.bufferbloat.net
Subject: Re: [Cake] New to cake. Some questions
Date: Fri, 10 Jun 2016 02:27:54 +0300 [thread overview]
Message-ID: <74C47155-52F4-4F20-9C55-BFC0AD817555@gmail.com> (raw)
In-Reply-To: <65184CD2-7205-4D93-9AD3-20F68C461E0E@gmx.de>
> why are the vdsl options suffixed with _ptm, but the atm options are not?
Because the “vcmux” and “llc” suffixes are sufficient to imply ATM cell framing.
> is the currently selected set of keywords minimal and complete?
I did some careful research back when I added that feature, including taking some suggestions from you, and according to that: yes, it is correct and complete, and every keyword is related to a real protocol. Though some are not widely used in practice, they *are* widely supported in ubiquitous consumer-grade equipment.
I haven’t seen any evidence to the contrary; if you have any, please show it, if not, PLEASE SHUT UP about it.
That, by the way, is *me* being blunt to the point of rudeness.
> why name something conservative that will for all peop;e not using an ATM link cost between 9 to 40% of goodput?
The use-case for the “conservative” keyword is essentially: “I know what the raw bitrate of the link is, but I have no sodding clue what overhead it has”. The goal is to prevent the dumb buffers elsewhere from filling up and undoing our good work.
Yes, it will overcompensate, leading to reduced throughput. That’s recognised and accepted as far as I’m concerned; the worst corner cases are with very small packets, which frankly matter less. If you don’t want overcompensation, figure out what the real overhead is and set that.
- Jonathan Morton
next prev parent reply other threads:[~2016-06-09 23:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 20:58 Dennis Fedtke
2016-06-09 21:30 ` moeller0
2016-06-09 22:45 ` Dennis Fedtke
2016-06-09 23:11 ` moeller0
2016-06-10 0:41 ` Dennis Fedtke
2016-06-10 5:16 ` moeller0
2016-06-10 0:49 ` Dennis Fedtke
2016-06-10 5:20 ` moeller0
2016-06-10 12:43 ` Dennis Fedtke
2016-06-10 13:02 ` moeller0
2016-06-10 14:05 ` Dennis Fedtke
2016-06-10 14:26 ` Sebastian Moeller
2016-06-10 22:01 ` Benjamin Cronce
2016-06-09 21:36 ` Kevin Darbyshire-Bryant
2016-06-09 22:17 ` Jonathan Morton
2016-06-09 22:49 ` moeller0
2016-06-09 23:27 ` Jonathan Morton [this message]
2016-06-10 8:19 ` 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=74C47155-52F4-4F20-9C55-BFC0AD817555@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
--cc=moeller0@gmx.de \
/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