From: Dave Taht <dave.taht@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] sqm-scripts on WRT1900AC
Date: Sat, 23 May 2015 23:44:33 -0700 [thread overview]
Message-ID: <CAA93jw5Ab1=eghXtd4Qjp9brHFe1yxkFSvjY+muLYXHjL4M-CA@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-PeerhPiWEhqWdGtrHN-fDMuQzObsCXq=83k+644yRSEg@mail.gmail.com>
yes, as it turned out I too was watching even linksys's unannounced
products enter the openwrt mainline with great joy (a core dev (imre)
does some work for them). I had fiddled with it a few months back...
... and I had tried to do a build w/cake+pie+fq_pie for it a few days
ago but the toolchain broke on my increasingly out of date main build
box (snapon). The right answer there is to get that stuff built out of
the main openwrt build system...
The marvell wifi driver for that box was dramatically improved last
christmas with fresh code from marvell, but I have not looked at it
closely to see how well the structure of the driver or the hardware
could align with the goals of make-wifi-fast. (has anyone? I am still
in pain from the ath10k work...)
the mvneta ethernet driver lacked bql when last I looked and was
really agressive about GRO offloads in particular. Both are easily
fixable.
And it has a fan. Hate fans. Amusingly (I guess), I had this same
chipset to fiddle with in the "mirabox" and it ran waaaay too hot.
It is not clear why you are getting an inaccurate rate out of it, either.
It is a leading candidate, but I would prefer to find a hardware
partner that cared about our issues enough to work with us, rather
than ignore us as netgear did.
next prev parent reply other threads:[~2015-05-24 6:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 5:17 [Cerowrt-devel] " Aaron Wood
2015-05-24 6:19 ` Aaron Wood
2015-05-25 23:55 ` [Cerowrt-devel] [Bloat] " David Lang
2015-05-29 8:34 ` Pedro Tumusok
2015-05-29 9:09 ` David Lang
2015-05-29 10:04 ` Pedro Tumusok
2015-05-29 20:26 ` David Lang
2015-06-01 8:47 ` Pedro Tumusok
2015-05-24 6:44 ` Dave Taht [this message]
2015-05-24 6:51 ` Aaron Wood
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='CAA93jw5Ab1=eghXtd4Qjp9brHFe1yxkFSvjY+muLYXHjL4M-CA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/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