Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] flow isolation for ISPs
Date: Thu, 6 Apr 2017 11:26:11 +0200	[thread overview]
Message-ID: <1E4563E2-63E2-419D-AFDD-8CD74F22539B@gmail.com> (raw)
In-Reply-To: <6F118C46-16DB-48AC-A90D-7E6D44B6D069@gmail.com>


> On Apr 6, 2017, at 11:11 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
> 
> On 6 Apr, 2017, at 11:27, Pete Heist <peteheist@gmail.com> wrote:
>> 
>> There is a table of member ID to a list of MAC addresses for the member, so if there could somehow be fairness based on that table and by MAC address, that could solve it, but I don’t see how it could be implemented.
> 
> One option would be to use HTB with FLOWER filters to sort out the subscribers into classes, and use Cake or fq_codel as a child qdisc per class.  Remember that Cake can be used in “unlimited” mode to rely on an external shaping source.

Looking at ‘man tc-flower’, it does sound like an option. I suppose that one instance of Cake per member will be somewhat similar computationally to one instance for multiple members. There will be additional memory used, and additional processing for the filters. This would also probably only be practical if members only use one access point, which I do think is typical. A few dozen filters and Cake instances might be ok, but I’m not sure about 800. :) We’ll see what we come up with. Thanks…


  reply	other threads:[~2017-04-06  9:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  8:27 Pete Heist
2017-04-06  8:39 ` David Lang
2017-04-06  8:48   ` Pete Heist
2017-04-06  8:57 ` Jonathan Morton
2017-04-06  9:04   ` Pete Heist
2017-04-06 10:26   ` Andy Furniss
2017-04-06  9:11 ` Jonathan Morton
2017-04-06  9:26   ` Pete Heist [this message]
2017-04-07  8:13     ` Pete Heist
2017-04-07  8:28       ` Jonathan Morton
2017-04-07  9:37         ` Pete Heist
2017-04-07 11:13           ` Sebastian Moeller
2017-04-07 11:42             ` Pete Heist
2017-04-08  6:16           ` Pete Heist
2017-04-07 10:56         ` John Sager
2017-04-06  9:33 ` Toke Høiland-Jørgensen
2017-04-06 10:26   ` Pete Heist
2017-04-06 10:50     ` Toke Høiland-Jørgensen
2017-04-06 11:34       ` Pete Heist
2017-04-06 12:14         ` Toke Høiland-Jørgensen
2017-04-06 13:30           ` Pete Heist
2017-04-06 13:42             ` Toke Høiland-Jørgensen
2017-04-06 13:50               ` Pete Heist
2017-04-06 14:41               ` Dave Taht
2017-04-06 12:48     ` Andy Furniss
2017-04-06 13:19 Konstantin Shalygin
     [not found] <mailman.340.1491486631.3609.cake@lists.bufferbloat.net>
2017-04-06 14:18 ` Pete Heist
2017-04-06 15:41   ` Andy Furniss

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=1E4563E2-63E2-419D-AFDD-8CD74F22539B@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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