Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: erik.taraldsen@telenor.com
Cc: me@lochnair.net, cake@lists.bufferbloat.net
Subject: Re: [Cake] Recomended HW to run cake and fq_codel?
Date: Wed, 3 May 2017 10:24:31 +0200	[thread overview]
Message-ID: <FD87BA88-0A6D-45D3-928F-E10164D5FF33@gmx.de> (raw)
In-Reply-To: <1493796453297.40351@telenor.com>

Hi Erik,

> On May 3, 2017, at 09:27, <erik.taraldsen@telenor.com> <erik.taraldsen@telenor.com> wrote:
> 
>> Fra: Sebastian Moeller <moeller0@gmx.de>
>> 
>>       Question: as an ISP what is your rationale to implement a shaper at the BRAS? Simply the fact that 
>> DSLAMs/MSANs are not capable to do it, or do you also need this to make sure there is always room for > your own VoIP packets?
> 
> At least the DSLAMs we use are basically switches.  Extremly limited QoS/shaping.  For a time we actually did not shape at the BRAS level and let the DSLAM's just drop whatever it could not push throug.  That was not a success.  It more or less behaved like a strictly policed access, which is not something you want.  So we went back to shaping at the BRAS.

	Ah, thanks for the insight, I had always assumed the rationale to be less obvious (like making VoIP more robust, keeping (D)DOS traffic out of the aggregation network; I had never assumed that dslams might simply be bad at traffic regulation ;) )

> 
> 
> 
>> 0) get rid of all non-essential encapsulations, use DHCP option 82 instead of PPPoE, rethink the need 
>> for VLAN tags,
> 
> Done, with the exeption of some legacy business usages.

	This is quite enlightened, great!

> 
> 
>> 1) make sure to properly account for all the quirks of ATM’s AAL5 encapsulation (see cake’s 
>> atm keyword or “man tc-stab”)
> 
> Noted.

	All I ever learned about this topic should be summarized in https://github.com/moeller0/ATM_overhead_detector/wiki .

> 
>> 2) preferably hoist your ADSL customers into the present and get your device manufacturers 
>> to implement PTM for adsl modems making 1) above much less involved ;)
> 
> To much legacy, so  more likely to migrate to VDSL across the board.

	Which effectively is the same for customers (except for unlucky ones at the end of very long lines, I believe); ATM deserves to retire ;)


> 
> Regarding BQL, we need the chipset vendors to do this.  In particular Broadcom.  We do try and influence them to do this, but we simply are a to small to get traction.

	Well, compared to most on this list you have a huge impact on the chipset vendors, so I hope for the best. Is there anybode besides Broadcom and Intel actually producing VDSL chipsets or is that the set of vendors that need to be convinced?

Best Regards
	Sebastian

> 
> 
> -Erik


  reply	other threads:[~2017-05-03  8:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.430.1493386395.3609.cake@lists.bufferbloat.net>
2017-04-28 16:39 ` Lochnair
2017-05-02 10:34   ` erik.taraldsen
2017-05-02 12:11     ` Nils Andreas Svee
2017-05-02 17:36       ` David Lang
2017-05-03  5:36       ` erik.taraldsen
2017-05-03  6:51         ` Sebastian Moeller
2017-05-03  7:27           ` erik.taraldsen
2017-05-03  8:24             ` Sebastian Moeller [this message]
2017-05-03 11:14               ` erik.taraldsen
     [not found] ` <mailman.433.1493397541.3609.cake@lists.bufferbloat.net>
2017-04-28 18:07   ` Tristan Seligmann
     [not found] <mailman.1.1493740801.18318.cake@lists.bufferbloat.net>
2017-05-02 18:44 ` Pete Heist
2017-05-03  5:59   ` erik.taraldsen
2017-05-03  7:15     ` Pete Heist
2017-05-03 10:03       ` Andy Furniss
2017-05-03 11:10       ` erik.taraldsen
2017-11-27  8:35     ` Dave Taht
2017-11-27 12:04       ` Jonathan Morton
2017-11-27 12:47         ` Pete Heist
2017-11-27 15:54           ` Sebastian Moeller
2017-11-27 16:12             ` Pete Heist
2017-11-27 18:28               ` Jonathan Morton
2017-11-27 21:49                 ` Pete Heist
     [not found] <mailman.1.1493827201.27042.cake@lists.bufferbloat.net>
2017-05-03 18:05 ` Pete Heist

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

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

  git send-email \
    --in-reply-to=FD87BA88-0A6D-45D3-928F-E10164D5FF33@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --cc=erik.taraldsen@telenor.com \
    --cc=me@lochnair.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