From: David Lang <david@lang.hm>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] More overhead keywords
Date: Mon, 18 May 2015 12:41:16 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1505181239090.30097@nftneq.ynat.uz> (raw)
In-Reply-To: <CAJq5cE2jzvS24kpAzocpbOj2V=aH+HQnHpg4P+bFfTgEc-0ErA@mail.gmail.com>
[-- Attachment #1: Type: TEXT/Plain, Size: 1174 bytes --]
On Mon, 18 May 2015, Jonathan Morton wrote:
> I've gone for the technical labels for three reasons. First, it reflects
> what's actually happening, which generally reduces confusion in the long
> run. Second, you might underestimate the number of ADSL ISPs worldwide, as
> well as the difficulty of keeping such a database up to date. Third, every
> DSL modem and ISP I know of has made it reasonably easy to discover at
> least the base encapsulations - autodetection of vcmux vs llc isn't
> absolutely reliable, for example. They might be less forthcoming about vlan
> and FCS, but one can make intelligent guesses here, based on whether it's a
> converged services ISP.
offer both the official labels and some easy-to-understand boxes to use
for example
underlying packet size (ATM = 48, Ethernet = 1500)
protocol overhead (various examples)
David Lang
> Ideally, we could do with a tool (at dslreports?) which makes detecting the
> actual overhead easier. This would be doable using small packets to magnify
> the differences.
>
> And if the user really can't work it out, they can always throw up their
> hands and specify "conservative".
>
> - Jonathan Morton
>
[-- Attachment #2: Type: TEXT/PLAIN, Size: 137 bytes --]
_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake
next prev parent reply other threads:[~2015-05-18 19:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-10 14:02 [Cake] openwrt build with latest cake and other qdiscs Alan Jenkins
2015-05-10 17:29 ` Alan Jenkins
2015-05-10 20:37 ` Dave Taht
2015-05-10 20:38 ` Dave Taht
2015-05-11 6:54 ` Sebastian Moeller
2015-05-10 21:46 ` Sebastian Moeller
2015-05-10 22:19 ` Dave Taht
2015-05-11 6:50 ` Sebastian Moeller
2015-05-11 7:01 ` Jonathan Morton
2015-05-13 6:43 ` Jonathan Morton
2015-05-14 9:19 ` Sebastian Moeller
2015-05-14 10:24 ` Jonathan Morton
2015-05-14 10:33 ` Alan Jenkins
2015-05-14 10:42 ` Jonathan Morton
2015-05-14 10:58 ` Sebastian Moeller
2015-05-14 13:12 ` Jonathan Morton
2015-05-14 14:57 ` Sebastian Moeller
2015-05-14 15:32 ` Jonathan Morton
2015-05-14 18:15 ` Sebastian Moeller
2015-05-14 22:06 ` Jonathan Morton
2015-05-15 2:27 ` Dave Taht
2015-05-15 21:49 ` Jonathan Morton
2015-05-14 9:50 ` Alan Jenkins
2015-05-18 0:49 ` [Cake] More overhead keywords Jonathan Morton
2015-05-18 7:27 ` Sebastian Moeller
2015-05-18 8:13 ` Jonathan Morton
2015-05-18 8:41 ` Sebastian Moeller
2015-05-18 19:41 ` David Lang [this message]
2015-05-18 19:57 ` Dave Taht
2015-05-19 10:14 ` Kevin Darbyshire-Bryant
2015-05-23 0:30 ` Dave Taht
2015-05-23 2:27 ` Jonathan Morton
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=alpine.DEB.2.02.1505181239090.30097@nftneq.ynat.uz \
--to=david@lang.hm \
--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