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:04:20 +0200	[thread overview]
Message-ID: <5E034518-C8CC-4A91-8F32-756BEA73BCD2@gmail.com> (raw)
In-Reply-To: <2EAA1B56-8CAD-4964-9DD7-99D54B82D44B@gmail.com>


> On Apr 6, 2017, at 10:57 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
> 
>> On 6 Apr, 2017, at 11:27, Pete Heist <peteheist@gmail.com> wrote:
>> 
>> Suppose there is a cooperative ISP that has some members who access the network through a single device (like a router with NAT), while others use multiple devices and leave routing to the ISPs routers. (No need to suppose, actually.)
>> 
>> There’s fairness at the IP address level (currently with esfq, maybe soon with Cake), but it's not fair that members with multiple devices effectively get one hash bucket per device, so if you have more devices connected at once, you win. 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.
>> 
>> Is it possible to customize the hashing algorithm used for flow isolation, either with Cake or some other way?
> 
> That is an important use-case, and one that Cake is not presently designed to explicitly accommodate.  Currently, the design assumes a single Cake instance per subscriber or household, and fairness between hosts within a household is assumed to be a relatively simple problem.
> 
> Also, Cake’s general philosophy of simplifying configuration means that it’s unlikely to ever support “lists” or “tables” of explicit parameters.  This is a conscious design decision to enable its use by relative non-experts.  Arguably, even some of the existing options could reasonably be streamlined away.
> 
> With that said, a related qdisc *with* such support is eminently feasible, and could easily be the focus of a project.  I think it would be worth gathering requirements for such a thing and considering potential funding sources.

I figured as much, but it’s good to know for sure, thanks!

Pete


  reply	other threads:[~2017-04-06  9:04 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 [this message]
2017-04-06 10:26   ` Andy Furniss
2017-04-06  9:11 ` Jonathan Morton
2017-04-06  9:26   ` Pete Heist
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=5E034518-C8CC-4A91-8F32-756BEA73BCD2@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