General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion
Date: Thu, 11 Jun 2015 13:16:15 +0200	[thread overview]
Message-ID: <20150611131615.20b1648f@redhat.com> (raw)
In-Reply-To: <0A0D06AB-CC83-4D99-80C6-8E7822C8707C@gmx.de>


On Sat, 6 Jun 2015 16:29:15 +0200 Sebastian Moeller <moeller0@gmx.de> wrote:

> On Jun 6, 2015, at 15:38 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> 
[...]
> > The problem I have is setting outbound rate limiting.  I was hoping
> > that 'cake' without the 'bandwidth' parameter would work on the
> > 'backpressure' from the ATM(?) driver, sadly this wasn't the case
> > and so setting a bandwidth limit (I'm not in a position to test the
> > new keywords for ATM encapsulation etc yet) was the only way
> > forward.  
> 
>  This is rather important to get right, ATM’s arcane 48/53
> encapsulation only leaves 100*48/53 = 90.5% of the sync rate for
> useable bits, and even those need to contain all the headers specific
> to your line (plus AAL5’s unfortunate choice of fitting each packet
> into an integer number of ATM cells), mean that without AQM taking
> the link layer encapsulation into account you need to aim for roughly
> 80-85% of the sync rates on and ATM link. With a link that disappears
> often I currently would recommend sqm-scripts as weapon of choice
> (you should be able to get cake into sqm-scripts) as the IFB needs to
> be set up again after the “connected” interface reappears, which
> current sqm-scripts should do for you...

That is true, the ATM overhead on ADSL is very important to get right
for your ratelimiting work as intended (that is you gain control over
the queue).

The iproute2 "tc" have supported option "linklayer atm" and "overhead"
for quite some time now (since 2008).  All the rate_tables based
schedulers (e.g. HTB, TBF) have these options.

There is also the more generic "stab" that allow linklayer adaptation to
work for any qdisc. See man tc-stab [1]

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Sr. Network Kernel Developer at Red Hat
  Author of http://www.iptv-analyzer.org
  LinkedIn: http://www.linkedin.com/in/brouer

[1] http://manpages.ubuntu.com/manpages/precise/man8/tc-stab.8.html

  parent reply	other threads:[~2015-06-11 11:16 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
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 [this message]
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=20150611131615.20b1648f@redhat.com \
    --to=jbrouer@redhat.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