From: Richard Smith <smithbone@gmail.com>
To: Dave Taht <dave.taht@gmail.com>,
Dheeran Senthilvel <dheeranmech@gmail.com>
Cc: lede-dev@lists.infradead.org,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [LEDE-DEV] WRT1900ACS Testing
Date: Tue, 14 Jun 2016 16:54:58 -0400 [thread overview]
Message-ID: <57606F22.2060704@gmail.com> (raw)
In-Reply-To: <CAA93jw6QAtWxGJsouztj0VgnrAjjhnW2TVmSmu933swjFGqq4g@mail.gmail.com>
On 05/20/2016 05:16 PM, Dave Taht wrote:
> We had found some pretty major performance problems on this hardware
> as of a few months ago. I am curious if they still exist? A whole
> bunch of benchmarks went by on the cerowrt-devel list, also.
Sorry I'm late on a response. I've been buried with work lately and
haven't been paying much attention to mailing lists.
> They were:
>
> 1) broken local ethernet network stack - running 4 copies of netperf
> against it - one would grab all the bandwidth and the other three
> barely even start or hang completely.
I confirmed your behavior on the 1900ACS using OpenWRT. I opted for
flent rrul_be and rrul tests rather than multiple netperfs though.
I'm happy to rejigger my build to be LEDE, rebuild, install, and run the
test again.
> 2) No BQL in the ethernet driver
Dunno about this one.
> 3) Wifi was horribly overbuffered in general
> 4) Wifi would crash against flent's rrul test.
I certainly saw these behaviors as well but I've not run rrul against
the WiFi in quite a while and I seem to remember a wireless firmware
update happening since I last ran the test.
I'll re-run and see.
--
Richard A. Smith
prev parent reply other threads:[~2016-06-14 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 21:16 Dave Taht
2016-05-20 22:09 ` David Lang
2016-06-14 20:54 ` Richard Smith [this message]
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=57606F22.2060704@gmail.com \
--to=smithbone@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dheeranmech@gmail.com \
--cc=lede-dev@lists.infradead.org \
/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