From: Sebastian Moeller <moeller0@gmx.de>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] VDSL
Date: Sat, 11 Jan 2014 19:40:31 +0100 [thread overview]
Message-ID: <BE1CF78D-1D02-43E5-BFD9-D3F653725B00@gmx.de> (raw)
In-Reply-To: <CCAC834F-77AB-46AB-A8EA-BC81D8721B35@gmail.com>
Hi Rich,
On Jan 11, 2014, at 18:55 , Rich Brown <richb.hanover@gmail.com> wrote:
> HI Sebastian,
>
>> Well, that looks like a decent recommendation for the wiki. The SQM configuration page still needs to expose all three values, atm, ethernet, and none so that people can actually change things...
>
> So two questions really:
>
> 1) (From my previous note) What’s the difference between the current “Ethernet” (for VDSL) and “None” link layer adaptations?
Currently, "none" completely disables the link layer adjustments, "ethernet" enables them, but will only use the overhead (unless you specify an tcMPU, but that is truly exotic).
>
> 2) When we distinguish the Ethernet/VDSL case, I would really like to use a different name from “Ethernet” because it seems confusingly similar to having a real Ethernet path/link (e.g., direct connection to internet backbone without any ADSL, cable modem, etc.)
On the one hand I agree, but the two options are called "ATM" (well for tc "adsl" is a valid alias for ATM) and "ethernet" if you pass them to tc (what we do), and I would really hate it to hide this under fancy names. I see no chance of renaming those options in tc, so we are sort of stuck with them and adding another layer of indirection seems too opaque to me. This is why I put some explanation behind the option names in the list box…
Best
Sebastian
>
> Thanks.
>
> Rich
next prev parent reply other threads:[~2014-01-11 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 16:29 Rich Brown
2014-01-11 16:54 ` Sebastian Moeller
2014-01-11 17:14 ` Rich Brown
2014-01-11 17:55 ` Rich Brown
2014-01-11 18:40 ` Sebastian Moeller [this message]
2014-01-11 19:06 ` Rich Brown
2014-01-11 19:57 ` Sebastian Moeller
2014-01-11 20:23 ` Aaron Wood
2014-01-11 22:15 ` Sebastian Moeller
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BE1CF78D-1D02-43E5-BFD9-D3F653725B00@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richb.hanover@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