From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] bufferbloat still misunderstood & ignored
Date: Thu, 29 Mar 2018 03:04:13 +0300 [thread overview]
Message-ID: <0FDFC78B-95A4-4A4E-8498-6C4AC9610BD0@gmail.com> (raw)
In-Reply-To: <CAA93jw6MfQ4jQRZvNr_UBWhg7Yc8LY+jR5y0iEm=HMLUq-gnUQ@mail.gmail.com>
> On 28 Mar, 2018, at 10:32 pm, Dave Taht <dave.taht@gmail.com> wrote:
>
> The two line method is quite common among gamers.
I'm pretty sure a single A&A ADSL connection costs less than two from a bargain-basement ISP, what with line rental factoring into the total price. Of course, not everyone is lucky enough to live in the UK and thus have access to A&A (myself included).
Something else to shoehorn into the Cake paper: as future work, an ISP-focused qdisc (or even a whole middlebox using commodity hardware) using a rearranged version of the technology proven in Cake. Cake itself is focused on managing a single link, whereas an ISP must deal with many subscriber links (with a finite variety of service tiers) sharing a backhaul link, with the link interface hardware itself being unable to avoid bufferbloat or to share bandwidth fairly when congestion occurs. The backhaul link might be to a local exchange, a shared cable medium, or a satellite hop.
- Jonathan Morton
next prev parent reply other threads:[~2018-03-29 0:04 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 [this message]
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
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=0FDFC78B-95A4-4A4E-8498-6C4AC9610BD0@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=toke@toke.dk \
/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