Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: "Rich Brown" <richb.hanover@gmail.com>,
	"cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>,
	"bloat" <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] fq_codel is SEVEN years old today...
Date: Tue, 14 May 2019 14:38:51 -0400 (EDT)	[thread overview]
Message-ID: <1557859131.759530583@apps.rackspace.com> (raw)
In-Reply-To: <2936.1557856670@turing-police>

[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]


Well, of all the devices in my house (maybe 100), only the router attached to the cable modem (which is a 2x GigE Intel Linux board based on Fedora 29 server with sch_cake configured) is running fq_codel. And setting that up was a labor of love. But it works a charm for my asymmetric Gigabit cable service.
 
My home's backbone is 10 GigE fiber, so I suppose fq_codel would be helpful for devices that run on 1 GigE subnets like my 2 802.11ac access points when talking to my NAS's.
However, the 802.11ac access point high speed functionality doesn't seem to be supportable by LEDE. So what can I do? 
 
I suppose I could stick some little custom Intel Linux 2x GigE devices between access points and the 10 GigE backbone, and put fq_codel in there.
 
My point is, to get the primary benefit of bufferbloat reduction, one has to stick little Linux boxes everywhere, because fq_codel is not supported except via DIY hacking.
 
And indeed, 10 GigE->1 GigE buffering does affect storage access latency in bad ways.
 
We see the same problem in datacenter networks that have excessive buffering - a famous switch company backed by Andy Bechtolsheim is really problematic because they claim building up huge buffers is a "feature" not a bug.
-----Original Message-----
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Sent: Tuesday, May 14, 2019 1:57pm
To: "Rich Brown" <richb.hanover@gmail.com>
Cc: "cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>, "bloat" <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] fq_codel is SEVEN years old today...



_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel
On Tue, 14 May 2019 08:16:06 -0400, Rich Brown said:

> Let's all pat ourselves on the back for this good work!

Do we have an estimate of what percent of connected devices
are actually using fq_codel or other modern anti-bloat methods?
I'm reasonably sure my TV, my PS3, and my PS4 are still
behind the curve.

[-- Attachment #2: Type: text/html, Size: 3645 bytes --]

  reply	other threads:[~2019-05-14 18:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 12:16 Rich Brown
2019-05-14 17:57 ` Valdis Klētnieks
2019-05-14 18:38   ` David P. Reed [this message]
2019-05-14 22:05     ` David P. Reed
2019-05-14 22:35       ` [Cerowrt-devel] [Bloat] " Toke Høiland-Jørgensen
2019-05-14 23:34         ` David P. Reed
2019-05-15  7:31           ` [Cerowrt-devel] (no subject) Sebastian Moeller
2019-05-15  7:58             ` [Cerowrt-devel] [Bloat] " 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           ` [Cerowrt-devel] [Bloat] fq_codel is SEVEN years old today 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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1557859131.759530583@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=richb.hanover@gmail.com \
    --cc=valdis.kletnieks@vt.edu \
    /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