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 17:54:00 +0100 [thread overview]
Message-ID: <49DBDBE7-BF76-4823-B723-670935A55833@gmx.de> (raw)
In-Reply-To: <4B0976EC-5224-4E81-B5DF-96A85424FB6E@gmail.com>
Hi Rich,
On Jan 11, 2014, at 17:29 , Rich Brown <richb.hanover@gmail.com> wrote:
> The VDSL option is burning up way too many of my brain cells. Given that VDSL may well use ATM, while VDSL2 is unlikely to use ATM, I think that it isn’t useful to include it as a top-level choice .
>
> In the new pages, I propose removing the VDSL choice, leaving:
>
> - “ATM (any kind of DSL link)” and
> - “None”
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...
>
> and letting people tune the settings after reading the “Everything you wanted to know…” page if they want to optimize.
Exactly, we still need options exposed for making this possible.
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_AQM_for_CeroWrt_310
>
> -and-
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Everything_you_wanted_to_know_about_Link_Layer_Adaptation
>
> Rich
Best Regards
Sebastian
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2014-01-11 16:54 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 [this message]
2014-01-11 17:14 ` Rich Brown
2014-01-11 17:55 ` Rich Brown
2014-01-11 18:40 ` Sebastian Moeller
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=49DBDBE7-BF76-4823-B723-670935A55833@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