From: Jonathan Morton <chromatix99@gmail.com>
To: Pete Heist <pete@eventide.io>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] bufferbloat still misunderstood & ignored
Date: Fri, 30 Mar 2018 18:29:41 +0300 [thread overview]
Message-ID: <7407AA6C-F02D-4EC6-BF0A-C50E7B365433@gmail.com> (raw)
In-Reply-To: <33060CFE-064A-426C-8F29-721DA2F058F3@eventide.io>
> On 30 Mar, 2018, at 11:05 am, Pete Heist <pete@eventide.io> wrote:
>
> So this mapping from member (subscriber) to their MACs or IPs would need to be configurable somewhere
Yes, I assumed something like that would be required to assign the correct tier of service (or BRAS rate) to each subscriber, and that's what makes it ISP-focused rather than end-user focused.
In Linux it appears to be possible to assign a flow mark (ie. a number) to packets using firewall rules or qdisc filters, and the subscriber ID and tier ID could probably be encoded into that. It would then only be necessary to inform the qdisc of this encoding (how many bits for each portion) and to define the tiers.
It would also probably be more appropriate to give an ISP-focused qdisc a sysfs configuration/stats interface with more flexibility than an iproute2 interface. I still think Cake works fine with iproute2 alone.
- Jonathan Morton
next prev parent reply other threads:[~2018-03-30 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.172.1522252010.3573.cake@lists.bufferbloat.net>
2018-03-28 15:53 ` Toke Høiland-Jørgensen
2018-03-28 19:32 ` Dave Taht
2018-03-29 0:04 ` Jonathan Morton
2018-03-29 0:26 ` Dave Taht
2018-03-29 0:53 ` Jonathan Morton
2018-03-29 1:07 ` Dave Taht
2018-03-29 9:07 ` Andy Furniss
2018-03-30 8:05 ` Pete Heist
2018-03-30 15:29 ` Jonathan Morton [this message]
2018-03-31 10:55 ` Toke Høiland-Jørgensen
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=7407AA6C-F02D-4EC6-BF0A-C50E7B365433@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=pete@eventide.io \
/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