Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] SQM Question #5: Link Layer Adaptation Overheads
Date: Sat, 4 Jan 2014 13:16:37 -0500	[thread overview]
Message-ID: <01558084-B7D8-448A-A4ED-CE36D18AAA97@gmail.com> (raw)

QUESTION #5: I still don’t have any great answers for the Link Layer Adaptation overhead descriptions and recommendations. In an earlier message, (see https://lists.bufferbloat.net/pipermail/cerowrt-devel/2013-December/001914.html and following messages), Fred Stratton described the overheads carried by various options, and Sebastian Moeller also gave some useful advice.

After looking at the options, I despair of giving people a clear recommendation that would be optimal for their equipment. Consequently, I believe the best we can do is come up with “good enough” recommendations that are not wrong, and still give decent performance.  

In this spirit, I have changed Draft #3 of the “Setting up SQM” page to reflect this understanding. See http://www.bufferbloat.net/projects/cerowrt/wiki/Setting_up_AQM_for_CeroWrt_310

	ADSL/ATM link: Choose “ADSL/ATM", and set Per Packet Overhead to 40
	VDSL2 link: Choose “VDSL”, and set Per Packet Overhead to 8
	Other kind of link (e.g., Cable, Fiber, Ethernet, other not listed): Choose “None (default)”, and set Per Packet Overhead to 0

NB: I have changed the first menu choice to “ADSL/ATM” and the second to “VDSL” in the description. I would ask that we change to GUI to reflect those names as well. This makes it far easier/less confusing to talk about the options. 

As always, I welcome help in setting out clear recommendations that work well for the vast majority of people who try CeroWrt. Thanks.

Rich

             reply	other threads:[~2014-01-04 18:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04 18:16 Rich Brown [this message]
2014-01-04 18:40 ` Fred Stratton
2014-01-06  3:29   ` Dave Taht
2014-01-06  9:52     ` Fred Stratton
2014-01-06 14:12       ` Sebastian Moeller
2014-01-06 14:22         ` Fred Stratton
2014-01-06 14:27           ` Sebastian Moeller
2014-01-07 11:08             ` David Personette
2014-01-07 11:34               ` Sebastian Moeller
2014-01-07 12:11                 ` David Personette
2014-01-07 13:02                   ` Sebastian Moeller
2014-01-07 13:43                     ` David Personette
2014-01-07 14:53                       ` Fred Stratton
2014-01-06 10:56     ` Sebastian Moeller
2014-01-06 15:03       ` Dave Taht
2014-01-06 15:25         ` Sebastian Moeller
2014-01-04 20:22 ` Sebastian Moeller
2014-01-06  3:46   ` Dave Taht
2014-01-06 12:28     ` Sebastian Moeller
2014-01-05  9:04 ` Sebastian Moeller
2014-01-11 16:29 ` Rich Brown
2014-01-11 16:51   ` 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=01558084-B7D8-448A-A4ED-CE36D18AAA97@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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