From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] next cerowrt release plan (of sorts)
Date: Thu, 26 Jul 2012 09:28:21 -0700 [thread overview]
Message-ID: <CAA93jw6GeTY6PpP=XPO6EGSoV6bn1ne=89+1qa3qKyUX=tYTfA@mail.gmail.com> (raw)
3.3.8-10 and -11 were not as good as I'd hoped.
I have been doing continuous integration while on this trip but have
not been in a position to test anything. And after -11 - well, I'm not
putting out anything without more serious testing.
The biggest issue we have is that there are multiple attempts in
motion to improve codel's behavior under load. We have a half dozen
competing ideas that all need simulation and testing. Nearly everybody
involved in the codel effort is at this upcoming ietf in vancouver, so
it is my hope that we can get together and get a set of common
simulations against the algorithmic variants, and decide on something
then.
So my plan is to get a cerowrt build out sometime next week. (aug 1-3)
An issue I fixed in the cerowrt source tree today is ipv6 default
routes weren't making it out via babel - It's apparently fixed now,
(thx to a patch from denis and now in the net-next linux tree).
Pretty much everything else is now stable - for example, dnsmasq 2.62
with AAAA reverse DNS and dhcpv6 support is now in openwrt mainline.
As things grow stabler in openwrt/cerowrt, the linux mainline tree
continues to advance. I'd like to backport Eric Dumazet's TCP small
queues work to this release of cerowrt, if I get time. This looks very
promising to reduce host bufferbloat still further:
http://lwn.net/Articles/506237/ - and de-heisenbug some tests.
BUT THAT'S IT.
For example: I am not planning on adding TCP fast open support on this
go-round. I do hope to ensure that TCP fast open can work, and perhaps
put means in play to measure it working or not, but that's it.
Anyway, I got off all my mailing lists while I took this break. So I
am out of touch. And refreshed.
If you have any bug fixes for cerowrt let me know soonest.
--
Dave Täht
next reply other threads:[~2012-07-26 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 16:28 Dave Taht [this message]
2012-07-30 17:31 ` Michael Richardson
2012-09-16 14:02 Dave Taht
2012-09-16 18:48 ` Maciej Soltysiak
2012-09-17 19:53 ` Dave Taht
2012-09-18 2:35 ` Stephen Walker
2012-09-17 17:02 ` Török Edwin
2012-09-17 17:04 ` Török Edwin
2012-09-17 17:24 ` 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='CAA93jw6GeTY6PpP=XPO6EGSoV6bn1ne=89+1qa3qKyUX=tYTfA@mail.gmail.com' \
--to=dave.taht@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