From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Thibaut <hacks@slashdirt.org>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Advantages to tightly tuning latency
Date: Tue, 21 Apr 2020 15:44:01 -0700 [thread overview]
Message-ID: <CAA93jw5yvybv+aXH4NLd1r_8xSP2CPwzeh0q6wm1c26jLPBxag@mail.gmail.com> (raw)
In-Reply-To: <603DFF79-D0C0-41BD-A2FB-E40B95A9CBB0@gmail.com>
On Tue, Apr 21, 2020 at 3:33 PM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 22 Apr, 2020, at 1:25 am, Thibaut <hacks@slashdirt.org> wrote:
> >
> > My curiosity is piqued. Can you elaborate on this? What does free.fr do?
>
> They're a large French ISP. They made their own CPE devices, and debloated both them and their network quite a while ago. In that sense, at least, they're a model for others to follow - but few have.
>
> - Jonathan Morton
they are one of the few ISPs that insisted on getting full source code
to their DSL stack, and retained the chops to be able to modify it. I
really admire their revolution v6 product. First introduced in 2010,
it's been continuously updated, did ipv6 at the outset, got fq_codel
when it first came out, and they update the kernel regularly. All
kinds of great features on it, and ecn is enabled by default for those
also (things like samba). over 3 million boxes now I hear....
with <1ms of delay in the dsl driver, they don't need to shape, they
just run at line rate using three tiers of DRR that look a lot like
cake. They shared their config with me, and before I lost heart for
future internet drafts, I'd stuck it here:
https://github.com/dtaht/bufferbloat-rfcs/blob/master/home_gateway_queue_management/middle.mkd
Occasionally they share some data with me. Sometimes I wish I lived in
paris just so I could have good internet! (their fiber offering is
reasonably buffered (not fq_codeled) and the wifi... maybe I can get
them to talk about what they did)
When free.fr shipped fq_codel 2 months after we finalized it, I
figured the rest of the world was only months behind. How hard is it
to add 50 lines of BQL oriented code to a DSL firmware?
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-04-21 22:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 18:22 Justin Kilpatrick
2020-04-21 18:40 ` Jonathan Morton
2020-04-21 18:44 ` Dave Taht
2020-04-21 22:25 ` Thibaut
2020-04-21 22:33 ` Jonathan Morton
2020-04-21 22:44 ` Dave Taht [this message]
2020-04-21 22:50 ` Dave Taht
2020-04-21 23:07 ` Jonathan Morton
2020-04-21 23:27 ` Dave Taht
2020-04-22 8:28 ` Thibaut
2020-04-22 9:03 ` Luca Muscariello
2020-04-22 14:48 ` Dave Taht
2020-04-22 15:28 ` Luca Muscariello
2020-04-22 17:42 ` David P. Reed
2020-04-23 9:29 ` Maxime Bizon
2020-04-23 11:57 ` Toke Høiland-Jørgensen
2020-04-23 12:29 ` Luca Muscariello
2020-04-23 12:33 ` Maxime Bizon
2020-04-23 16:42 ` Toke Høiland-Jørgensen
2020-04-23 17:31 ` Maxime Bizon
2020-04-23 18:30 ` Sebastian Moeller
2020-04-23 21:53 ` Maxime Bizon
2020-04-23 18:35 ` Toke Høiland-Jørgensen
2020-04-23 21:59 ` Maxime Bizon
2020-04-23 23:05 ` Toke Høiland-Jørgensen
2020-04-23 23:11 ` Dave Taht
2020-04-23 16:28 ` Dave Taht
2020-04-21 23:06 ` Justin Kilpatrick
2020-04-21 23:19 ` Dave Taht
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=CAA93jw5yvybv+aXH4NLd1r_8xSP2CPwzeh0q6wm1c26jLPBxag@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=hacks@slashdirt.org \
/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