From: Rich Brown <richb.hanover@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Perfection vs. Good Enough
Date: Sat, 11 Jan 2014 11:31:59 -0500 [thread overview]
Message-ID: <3BF82F93-07EC-44F8-AF98-2FD156A9A43F@gmail.com> (raw)
Folks,
I am so pleased with the state of CeroWrt. The software has improved enormously, to the point that we all get really good performance from our routers at home. If you want a real eyeful of the progress we’ve made, check list at the bottom of the Release Notes: http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_310_Release_Notes
CeroWrt is working great. We have two great testimonials for how it has improved network performance (from Fred Stratton and David Personnette, see https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-January/001961.html and https://lists.bufferbloat.net/pipermail/cerowrt-devel/2014-January/001970.html)
I have been using 3.10.24-8 at home without hiccups (after I turned on SQM :-) since it was shipped. We’ve got a really great program.
But - I’m afraid we’re letting perfection be the enemy of the good. Here are a couple indications:
- The rest of the world doesn’t know about this good work. If you look at the front page of the site, we’re recommending CeroWrt 3.7.5-2 from last February. It has Codel, but not much more. Our understanding of the world has expanded by an order of magnitude, but we’re not making it available to anyone.
- The entire discussion of link layers has held us back. That’s why I proposed to cut back the choices to ATM and None, and let people figure out the details if they want to/have time to optimize.
- We have tons of updated modules (dnsmasq, IPv6, quagga, mosh) which we should get out to the world.
- The entire product is much tighter, works better, and we can be proud of it. As Dave Täht pointed out in a recent note:
> Compared to the orders of magnitude we already get from fq codel, the sum benefit
> of these [Link Layer Adaptation] fixes is in the very small percentage points.
This is true of the entire CeroWrt build.
Proposal:
We should “finish up the last bits” to make 3.10.24-8 (or a close derivative) be a stable release. It has been working fine AFAIK for lots and lots of us. It certainly has been as well tested as other branches. I see the following:
- Look through the release notes (very bottom of the page at the URL above) and review the items that Dave was worried about for the 3.10.24-8 release
- Make a decision on Link Layer Adaptation choices, and implement it.
- What else?
Best,
Rich
next reply other threads:[~2014-01-11 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 16:31 Rich Brown [this message]
2014-01-11 18:08 ` Theodore Ts'o
2014-01-11 18:30 ` Sebastian Moeller
2014-01-11 18:47 ` Rich Brown
2014-01-11 20:03 ` Sebastian Moeller
2014-01-13 0:10 ` David Lang
2014-01-13 3:14 ` Theodore Ts'o
2014-01-13 3:49 ` Michael Richardson
2014-01-13 0:02 ` David Lang
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=3BF82F93-07EC-44F8-AF98-2FD156A9A43F@gmail.com \
--to=richb.hanover@gmail.com \
--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