Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] fq_codel is *three* years old today
Date: Thu, 14 May 2015 14:38:52 +0100	[thread overview]
Message-ID: <5554A56C.5010403@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <24D7CF8A-6FAE-47D8-A9EE-1C1B0734D1E6@gmail.com>

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



On 14/05/15 13:11, Rich Brown wrote:
> Folks,
>
> Today is the third anniversary of the announcement of a testable fq_codel (see https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-May/002984.html et. seq.)
Happy Birthday! :-)
> - Speaking of which, the new DSLReports Speed Test has recently stirred things up. Not only do we have an attractive tool that we can recommend to friends, but people are getting a little hot under the collar when they see the crummy performance of the router that they just paid dearly for. See, for example, http://www.dslreports.com/forum/r30051856-Connectivity-Buffer-Bloat
>
>

Not just dslreports.  Thinkbroadband (quite popular in the UK) have been 
working on a new HTML5 based 'speed/latency' test (they've been 
collecting data for a few months) 
http://www.thinkbroadband.com/speedtest.html

It looks like it's still in progress and only gives a 'bufferbloat 
rating' rathing than DSLReport's pretty graphs, BUT it is adding to the 
tide of bufferbloat awareness which can only be a good thing.

My awareness and interest has certainly been piqued over the past few 
months.  Dave & Jim's explanations of bufferbloat have been avid 
reading/viewing here, as has the increasing alarm at the poor^H^H^H^H 
non-existent support of standard CPE routing devices (I now won't touch 
anything older than linux 3.0 based)  'Friends don't let friends run 
factory firmware' (especially parents) has been the motivation for 
switching to OpenWrt as well as bufferbloat improvements (though I'm 
also concerned by coding monocultures) Most things have stretched my 
circa 1990 unix sys admin skills (used to sysadmin before another path 
took hold) but picking up little tidbits of info from this list and 
others, I hope to be able to contribute in the near future.

Sincerest thanks to (in no particular order) Jim, Dave, Toke, Alan & all 
the crew here for working on the bufferbloat problem.

Kevin


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4791 bytes --]

  reply	other threads:[~2015-05-14 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 12:11 Rich Brown
2015-05-14 13:38 ` Kevin Darbyshire-Bryant [this message]
2016-05-14 13:18 ` [Cerowrt-devel] Fwd: fq_codel is *four* " Rich Brown
2017-05-14 12:31   ` [Cerowrt-devel] fq_codel is *five* " Rich Brown
2017-05-15  1:04     ` [Cerowrt-devel] [Bloat] " Stephen Hemminger

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=5554A56C.5010403@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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