General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ADSL, ATM drivers, bloat, education & confusion
Date: Sat, 6 Jun 2015 16:46:20 +0100	[thread overview]
Message-ID: <557315CC.1060405@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <0A0D06AB-CC83-4D99-80C6-8E7822C8707C@gmx.de>

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



On 06/06/15 15:29, Sebastian Moeller wrote:
> 1) ATM interface 'backpressure' - is this Byte Queue Limits? (ifxmips_atm)
> 	Is there actual backpreassure from your ATM diver at all? As rar as I know france’s free had their boxes ATM driver modified to keep buffering low, and I believe David Woodhouse dd some work on another driver/the generic ATM layer, but I am not sure that any ATM driver actually defaults to sane buffering and sane back pressure.
That was my sort of point.  On 'planet Kevin' (don't go there) the ATM 
driver would *know* the link is busy, or how many bytes it still had to 
shove over it and could offer some clue back up the stack to not bloat.  
I thought that's what BQL was supposed to do.  Or another way of 
viewing:  If ethernet interfaces ideally implement BQL why shouldn't ATM?

>
>
> 	How this is supposed to work? In an ideal work the CPE and the DSLAM would not over-buffer and www would not have to dedicate grey matter to work around their sort-commings ;) But as far as I can tell DSL sync rates for many lines are stable over weeks to months, so setting the shaper rarely is sufficient. Like when you notice that latency under load got worse…
Well again on 'planet Kevin' the CPE is OpenWrt.  Apparenly it's under 
my control but I'm fighting my own lack of abilities, trying to sprint a 
marathon before I can even crawl.  Looking at kernel sources when I can 
barely get 'hello world' to compile & run is asking for trouble :-)  
About a day ago I didn't know what an SKB was. 
https://www.coverfire.com/articles/queueing-in-the-linux-network-stack/ 
has been a revelation.
>
> Best Regards
> 	Sebastian
>



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]

  reply	other threads:[~2015-06-06 15:46 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 [this message]
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=557315CC.1060405@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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