Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Andy Furniss <adf.lists@gmail.com>
To: Pete Heist <peteheist@gmail.com>, erik.taraldsen@telenor.com
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Recomended HW to run cake and fq_codel?
Date: Wed, 3 May 2017 11:03:24 +0100	[thread overview]
Message-ID: <18f4b94c-0dc7-fb76-6ea8-65b3c759bda2@gmail.com> (raw)
In-Reply-To: <C0580931-127C-4ECF-A637-9AEA7DE92D40@gmail.com>

Pete Heist wrote:

> Another option for ISPs (failing AQM support in the devices, and
> instead of deploying devices on the customer side), could be to
> provide each customer a queue that’s tuned to their link rate. There
> could be an HTB tree with classes for each customer and Cake at the
> leafs. Knowing each customer’s link rate (assuming it’s not
> variable)

FWIW, on the narrow knowing variable rate point, in the UK DSLAMs use (I
think) TR101 to report sync rates to ISPs.
It has always been the case that BRAS is set with this, my ISP does also
use it to do downstream (for me, egress for them) QOS.
Of course they need (expensive?) kit to mark, and DPI/rules to classify
traffic ....
They use Ellacoyas. I don't know if they do the actual shaping or just
the classification and marking.


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

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2017-11-28 18:15                   ` [Cake] Simple metrics Dave Taht
2017-11-28 22:14                     ` Pete Heist
2017-11-28 22:41                       ` Dave Taht
2017-11-29  8:08                         ` Sebastian Moeller
     [not found] <mailman.1.1493827201.27042.cake@lists.bufferbloat.net>
2017-05-03 18:05 ` [Cake] Recomended HW to run cake and fq_codel? Pete Heist
     [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
2017-05-03 11:14               ` erik.taraldsen
     [not found] ` <mailman.433.1493397541.3609.cake@lists.bufferbloat.net>
2017-04-28 18:07   ` Tristan Seligmann

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=18f4b94c-0dc7-fb76-6ea8-65b3c759bda2@gmail.com \
    --to=adf.lists@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=erik.taraldsen@telenor.com \
    --cc=peteheist@gmail.com \
    /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