General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: moeller0 <moeller0@gmx.de>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Updates on www.bufferbloat.net
Date: Thu, 7 Jul 2016 13:57:45 -0400	[thread overview]
Message-ID: <6282F017-157E-4A21-BF96-B6DFCBB88CC7@gmail.com> (raw)
In-Reply-To: <5B859436-AC4A-44CE-9218-981F9C1855B1@gmx.de>

Hi Sebastian,

> On Jul 7, 2016, at 11:55 AM, moeller0 <moeller0@gmx.de> wrote:
> 
> 	I see that there is a link to https://wiki.openwrt.org/doc/howto/sqm on this page, and that reminds me, could you add a link to https://github.com/moeller0/ATM_overhead_detector to that openwrt page please? Probably in the section titled “Link Layer Adaptation - the details…”
> Here is a quick draft:
> 
> For true ATM links one often can measure the real per packet overhead empirically, see https://github.com/moeller0/ATM_overhead_detector for further information how to do that.
> 
> 	And while at it the following might also need a small upgrade:
> original: “SQM can also account for the overhead imposed by "Ethernet with overhead" (mostly VDSL) links. Cable Modem, Fiber, and direct Ethernet connections generally do not need any kind of link layer adaptation."
> 
> proposal: "SQM can also account for the overhead imposed by "Ethernet with overhead" (mostly VDSL) links. Cable Modems (docsis) are known to typically use 28 Byte of overhead in the upstream direction but only 14 in the downstream direction. If your version of SQM only supports to specify one value for the overhead, select 28 Bytes… Fiber, and direct Ethernet connections generally do not need any kind of link layer adaptation.”
> 
> 	Thanks to Greg we learned something about docsis and it would be a pity not to pass this information on to our users… (Note to self I need to allow independent overhead control for ingress and egress in sqm-scripts and the GUI).

I took a stab at it. Let me know if I got it right: https://wiki.openwrt.org/doc/howto/sqm#sqmlink_layer_adaptation_tab

Thanks.

Rich

      reply	other threads:[~2016-07-07 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 15:12 Rich Brown
2016-07-07 15:55 ` moeller0
2016-07-07 17:57   ` Rich Brown [this message]

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6282F017-157E-4A21-BF96-B6DFCBB88CC7@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --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