General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion
Date: Sat, 6 Jun 2015 16:53:43 +0300	[thread overview]
Message-ID: <CAJq5cE1LWz_LMb8rGLMuU5doQZw9uqxWgL=BMi0m=r4DAe3TcQ@mail.gmail.com> (raw)
In-Reply-To: <5572F7E0.3060602@darbyshire-bryant.me.uk>

[-- Attachment #1: Type: text/plain, Size: 796 bytes --]

Ideally, one would read the raw sync rate out of the modem (there has to be
a way to do that, since it is able to report it in the web interface), and
use that to set cake's bandwidth parameter. You could update it
periodically using "tc qdisc change ...".

You will need to set the overhead calculation correctly, probably using
"pppoa-vcmux" or similar, depending on precisely what encapsulation your
ISP uses. If you're not confident about that, specify "conservative" to
begin with. Once you have that, you can experiment to see how much you need
to reduce the raw sync rate to achieve full bottleneck control - hopefully
not much, at most 1%.

The same approach would also work for inbound if necessary, except that you
would need to reduce the raw sync rate rather more.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 910 bytes --]

  reply	other threads:[~2015-06-06 13:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06 13:38 Kevin Darbyshire-Bryant
2015-06-06 13:53 ` Jonathan Morton [this message]
2015-06-06 14:30   ` Sebastian Moeller
2015-06-11 11:24     ` Jesper Dangaard Brouer
2015-06-11 11:57       ` Sebastian Moeller
2015-06-11 14:14         ` Tristan Seligmann
2015-06-11 21:03           ` Sebastian Moeller
2015-06-12  6:45             ` Jesper Dangaard Brouer
2015-06-06 15:04   ` Sebastian Moeller
2015-06-06 14:29 ` Sebastian Moeller
2015-06-06 15:46   ` Kevin Darbyshire-Bryant
2015-06-06 15:50     ` Dave Taht
2015-06-06 18:14     ` Sebastian Moeller
2015-06-07 13:29       ` Kevin Darbyshire-Bryant
2015-06-11 11:16   ` Jesper Dangaard Brouer
2015-06-11 11: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/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='CAJq5cE1LWz_LMb8rGLMuU5doQZw9uqxWgL=BMi0m=r4DAe3TcQ@mail.gmail.com' \
    --to=chromatix99@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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