From: Dave Taht <dave.taht@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Rich Brown" <richb.hanover@gmail.com>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] fq_codel is SEVEN years old today...
Date: Sat, 18 May 2019 13:36:02 +0200 [thread overview]
Message-ID: <CAA93jw7oNi84n_WiDoLdGuyMguZoEuqYB1Ci=kGLwsujd51H2A@mail.gmail.com> (raw)
In-Reply-To: <1557876841.69888745@apps.rackspace.com>
The future seemed so bright after free.fr deployed it so fast. And so
far as I can tell, fq_codelis ubiquitous across all of linux and linux
containers and vms, and we've headed off major trouble at the wifi
pass with the OSX and QCA (ath9k, ath10k) implementations. 10s of
millions deployed - but where it's most needed, it's not, and ISPs
mostly ship it not.
So while I do take heart in the enormous deployment and figure we'll
turn the corner in the next year or seven on these other devices, I
was grumpily looking over:
http://conferences.sigcomm.org/sigcomm/2014/doc/slides/137.pdf
again today, and wishing we had some way of addressing the structural
problems we have with academic and industry research in general.
On Wed, May 15, 2019 at 1:34 AM David P. Reed <dpreed@deepplum.com> wrote:
>
>
>
> Ideally, it would need to be self-configuring, though... I.e., something
> like the IQRouter auto-measuring of the upstream bandwidth to tune the
> shaper.
>
>
>
> Sure, seems like this is easy to code because there are exactly two ports to measure, they can even be labeled physically "up" and "down" to indicate their function.
>
>
> For reference, the GL.iNet routers are tiny and nicely packaged, and run
> OpenWrt; they do have one with Gbit ports[0], priced around $70. I very
> much doubt it can actually push a gigabit, though, but I haven't had a
> chance to test it. However, losing the WiFi, and getting a slightly
> beefier SoC in there will probably be doable without the price going
> over $100, no?
>
>
>
> I assume the WiFi silicon is probably the most costly piece of intellectual property in the system. So yeah. Maybe with the right parts being available, one could aim at $50 or less, without sales channel markup. (Raspberry Pi ARM64 boards don't have GigE, and I think that might be because the GigE interfaces are a bit pricey. However, the ARM64 SoC's available are typically Celeron-class multicore systems. I don't know why there aren't more ARM64 systems on a chip with dual GigE, but I suspect searching for them would turn up some).
>
> -Toke
>
> [0] https://www.gl-inet.com/products/gl-ar750s/
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
prev parent reply other threads:[~2019-05-18 11:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 12:16 [Bloat] " Rich Brown
2019-05-14 17:57 ` [Bloat] [Cerowrt-devel] " Valdis Klētnieks
2019-05-14 18:38 ` David P. Reed
2019-05-14 22:05 ` David P. Reed
2019-05-14 22:35 ` Toke Høiland-Jørgensen
2019-05-14 23:34 ` David P. Reed
2019-05-15 7:31 ` [Bloat] (no subject) Sebastian Moeller
2019-05-15 7:58 ` Dave Taht
2019-05-15 8:30 ` Sebastian Moeller
2019-05-16 22:01 ` Jonathan Foulkes
2019-05-18 22:36 ` David P. Reed
2019-05-18 22:57 ` Jonathan Morton
2019-05-18 23:06 ` Jonathan Morton
2019-05-19 2:06 ` David P. Reed
2019-05-16 16:40 ` Jonathan Foulkes
2019-05-16 22:12 ` Sebastian Moeller
2019-05-18 11:36 ` Dave Taht [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7oNi84n_WiDoLdGuyMguZoEuqYB1Ci=kGLwsujd51H2A@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--cc=richb.hanover@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