From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] delays: trying to beat a performance issue on ipv6
Date: Thu, 12 Apr 2012 09:35:27 -0700 [thread overview]
Message-ID: <CAA93jw6TvLE-sq0TooeGqDb67g3ZnUAASa00BXxKOJSDcnfjzw@mail.gmail.com> (raw)
I had intended to work on a few other things, but we're making good
progress on making ipv6 perform well on this platform
http://www.bufferbloat.net/issues/360
However if anybody's got a monster 6 or 8 or 10 or 12 core box(es) and
tons of ram, it would be really handy right now, not just to turn
around some quick kernel patches, but cope with the ongoing buildbot
problem....
http://buildbot.openwrt.org:8010/tgrid
Due to these two issues.
There is now no way I'll have a build I'd consider 'beta' quality by
friday, however. I'd hoped to land the last three big items on my todo
list by today and haven't got anywhere. (kernel hacking appears to be
easier than what's on the backlog)
So we're going to end up with another small step towards a release
friday or saturday, if we're lucky.
Perhaps late next week we'll have something that is actually beta
quality. There is a pile of patches queued up for linux 3.2.2, the
core ones I tested with the last build.
If I could convince some folk to review the bug list
https://www.bufferbloat.net/projects/cerowrt/issues
to comment, prioritize, (or close!), I'd appreciate it.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
reply other threads:[~2012-04-12 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw6TvLE-sq0TooeGqDb67g3ZnUAASa00BXxKOJSDcnfjzw@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