From: Pete Heist <pete@eventide.io>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] bufferbloat still misunderstood & ignored
Date: Fri, 30 Mar 2018 10:05:28 +0200 [thread overview]
Message-ID: <33060CFE-064A-426C-8F29-721DA2F058F3@eventide.io> (raw)
In-Reply-To: <B02D8A8C-34B9-408B-A9C1-0040423F736F@gmail.com>
> On Mar 29, 2018, at 2:53 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 29 Mar, 2018, at 3:26 am, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> A finicky bit would be who to penalize when the underlying medium
>> (shared cable) is oversubscribed.
>
> Two obvious reasonable solutions: share equally per subscriber, or share proportionately to provisioned bandwidth per subscriber. Either should be fairly straightforward to implement in an integrated qdisc, and either would penalise the (instantaneously) heaviest users before affecting normal or light users.
As one use case, FreeNet Liberec, the co-operative ISP I use, would use the “shared equally” option. The important part for them is that some members access from a single CPE device and others from multiple devices whose IPs are handed out by FreeNet’s routers. There’s a db with mappings from member ID to their MACs, I believe, which is used to generate various config files. So this mapping from member (subscriber) to their MACs or IPs would need to be configurable somewhere, which was already eluded to earlier.
Personally, I like the idea of _only_ offering equal sharing, as it’s easiest to implement and serves a social purpose.
next prev parent reply other threads:[~2018-03-30 8:05 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 [this message]
2018-03-30 15:29 ` Jonathan Morton
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=33060CFE-064A-426C-8F29-721DA2F058F3@eventide.io \
--to=pete@eventide.io \
--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