From: Dave Taht <dave.taht@gmail.com>
To: fuller@beif.de
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Using cake to shape 1000’s of users.
Date: Tue, 17 Jul 2018 09:59:12 -0700 [thread overview]
Message-ID: <CAA93jw6xh4rquGA+hSOKjLB_SYObe8p2+-aw_0+wk2YshWiUgA@mail.gmail.com> (raw)
In-Reply-To: <1357421162.31089.1531812291583@webmail.strato.de>
On Tue, Jul 17, 2018 at 12:24 AM Felix Resch <fuller@beif.de> wrote:
>
> since commercial interest is involved, see here https://lists.bufferbloat.net/pipermail/cake/2018-June/003861.html
I grew that list substantially in the ending talk. It was motivating.
:) I am thinking of doing something similar (with editorial comments)
pointing
to each of dslreports' values per ISP, like, for example, leveraging
http://www.dslreports.com/speedtest/results/bufferbloat?up=1
To kvetch while pointing further to stuff like:
http://www.dslreports.com/speedtest/results/isp/r3910-google-fiber
http://www.dslreports.com/speedtest/results/isp/r2784-t-mobile
http://www.dslreports.com/speedtest/results/isp/r896-sonic
http://www.dslreports.com/speedtest/results/isp/r1579-Comcast%20XFINITY
That angst out, ISPs and vendors that want to work with us to
establish requirements and code for a transparent
bridge/veth/cake-like thing are very welcome at any point! The core
factor stopping us from even trying isn't lack of money or time... it
is not knowing of *any* head-end equipment (DSLAM/CMTS/GPON/etc) that
could be modified by us to have better queue management in the first
place, and a transparent bridge seems second best, at best, with
complexities involving ipv6 and ipv4 support, sag, nat, vlans, etc,
etc - so we've focused on fixing the edge device itself, and making
available published open source code and standards in the hope that
some head-end vendor would pick it up... after being suitably nagged
by their ISP customers. Or the sandvine type middlebox folk.
Also, in terms of angst, we hope merely that ISPs would start
supplying CPE that has our stuff in it (particularly since the
aftermarket already has it, and it works in even the cheapest boxes
made today), and either autoconfigure to their set rates, with cake,
or supply that information to their end users to configure. It's been
6 years since the code hit the embedded world.... I'm pleased to say
that "fq_codel for wifi" derivatives seem to propagating rapidly, at
least. Maybe a fortigate or barracuda will ship some kind of smart
queue management one day soon... if enough customers ask for it.
example: https://forum.fortinet.com/tm.aspx?m=163978
on the transparent bridge front... Linux has issues scaling to high
rates *on the receive path* at 10gigE+ speeds.
I've certainly lain awake at night dreaming of what we could do with a
smart line card for a cmts, or even a small dslam.
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next prev parent reply other threads:[~2018-07-17 16:59 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 7:24 Felix Resch
2018-07-17 16:59 ` Dave Taht [this message]
2018-07-26 15:46 ` Dan Siemon
2018-07-26 15:48 ` Dave Taht
2018-07-26 18:07 ` Dan Siemon
2018-07-28 15:51 ` Dave Taht
2018-07-28 16:11 ` Jonathan Morton
2018-07-28 16:36 ` Dave Taht
2018-07-26 17:42 ` Toke Høiland-Jørgensen
2018-07-26 18:10 ` Dan Siemon
2018-07-26 21:09 ` Toke Høiland-Jørgensen
2018-07-26 21:38 ` Jonathan Morton
2018-07-27 9:25 ` Pete Heist
2018-07-27 14:04 ` Dan Siemon
2018-07-27 18:58 ` Jonathan Morton
2018-07-28 8:56 ` Toke Høiland-Jørgensen
2018-07-28 15:04 ` Dave Taht
2018-07-28 16:19 ` Jonathan Morton
2018-07-28 16:39 ` Dave Taht
2018-07-28 17:01 ` Pete Heist
2018-07-28 17:37 ` Pete Heist
2018-07-28 17:52 ` Dave Taht
2018-07-28 17:56 ` Dave Taht
2018-07-28 18:12 ` Toke Høiland-Jørgensen
2018-07-29 0:17 ` Pete Heist
2018-07-29 19:14 ` Toke Høiland-Jørgensen
2018-07-30 9:14 ` Pete Heist
2018-07-30 10:09 ` Sebastian Moeller
2018-07-30 10:55 ` Toke Høiland-Jørgensen
2018-07-30 11:05 ` Pete Heist
2018-07-30 11:28 ` Toke Høiland-Jørgensen
2018-07-30 22:10 ` Pete Heist
2018-07-30 22:17 ` Toke Høiland-Jørgensen
2018-07-31 7:31 ` Jonathan Morton
2018-07-30 10:55 ` Pete Heist
2018-07-30 11:05 ` Jonathan Morton
2018-07-28 17:53 ` Jonathan Morton
2018-07-28 18:07 ` Dave Taht
2018-07-28 18:17 ` Toke Høiland-Jørgensen
2018-07-28 19:35 ` [Cake] 1000s " Dave Taht
2018-07-29 23:24 ` [Cake] Using cake to shape 1000’s " Dave Taht
2018-08-07 1:46 ` Dan Siemon
2018-07-28 7:18 ` Pete Heist
2018-07-28 8:06 ` Jonathan Morton
2018-07-28 16:41 ` Pete Heist
2018-07-28 17:32 ` [Cake] isp economics Dave Taht
2018-07-28 18:39 ` Pete Heist
2018-07-28 19:03 ` Dave Taht
2018-07-28 20:00 ` Pete Heist
2018-07-29 5:49 ` Loganaden Velvindron
2018-07-28 19:09 ` Dave Taht
-- strict thread matches above, loose matches on Subject: below --
2018-07-16 18:39 [Cake] Using cake to shape 1000’s of users Mike
2018-07-16 19:01 ` Jonathan Morton
2018-07-16 19:13 ` Michel Blais
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=CAA93jw6xh4rquGA+hSOKjLB_SYObe8p2+-aw_0+wk2YshWiUgA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=fuller@beif.de \
/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