From: Richard Smith <smithbone@gmail.com>
To: Dave Taht <dave.taht@bufferbloat.net>, Hannu Nyman <hannu.nyman@iki.fi>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [OpenWrt-Devel] [RFC PATCH] packages: Smart Queue Management for AQM Packet Scheduling and Qos from CeroWrt
Date: Thu, 09 Oct 2014 13:09:11 -0400 [thread overview]
Message-ID: <5436C137.8070706@gmail.com> (raw)
In-Reply-To: <20141009030125.GA19113@lists.bufferbloat.net>
On 10/08/2014 11:01 PM, Dave Taht wrote:
> Excellent. I'd *really* like to get some testers doing ingress shaping
> at above 60-80mbits, which seems to be a brick wall we've hit on
> the ar71xx and octeon, on other platforms like the arm and x86.
I can do ingress shaping tests at above 80mbits at work since we now
have a 100mbit downlink, but I don't have cerowrt hardware that runs
fast enough to keep up. Also I would only be able to do them on the
weekend or late at night when no one else is in the office when I can
swap out the router. I can't leave experimental setups alone running
our office link.
FYI: I've purchased a Nighthawk x6 for some testing. I did x6 even
though its CPU speed is slower than the x4 because I want to see if the
twin 5Ghz radios and the promise of automatic load balancing helps on
the wireless side (we have a lot of 5Ghz wireless clients) If it
doesn't hold up as a router we may still use it as just an AP.
Like you mentioned the stock firmware is not the greatest and there's no
actual bandwidth control settings. Hopefully openwrt support will show
up soon.
My initial tests with Gbit pipes on either side are certainly impressive
as it can route at over 900 Mbs while keeping latency at 12ms or lower.
Tonight I'm planning on testing it with my home Comcast cable link and
see if the low-latency holds.
--
Richard A. Smith
next prev parent reply other threads:[~2014-10-09 17:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1396119385-16871-1-git-send-email-dave.taht@bufferbloat.net>
[not found] ` <1396119385-16871-2-git-send-email-dave.taht@bufferbloat.net>
[not found] ` <CAFE24U3s=z4jZkXMFU4xUyPyQ5fj95zOVxS7oBHGFuOp-FKXqw@mail.gmail.com>
[not found] ` <20140330222952.GA26806@lists.bufferbloat.net>
[not found] ` <542C2786.6090704@gmail.com>
2014-10-02 1:49 ` Dave Taht
2014-10-02 3:46 ` Alpha Sparc
2014-10-02 11:54 ` David Lang
2014-10-02 14:05 ` Sebastian Moeller
2014-10-06 16:02 ` Richard A. Smith
2014-10-06 19:41 ` Sebastian Moeller
2014-10-09 16:42 ` Richard Smith
2014-10-09 17:57 ` Sebastian Moeller
2014-10-09 18:05 ` Luis E. Garcia
2014-10-09 20:59 ` Sebastian Moeller
2015-02-13 2:02 ` Luis E. Garcia
2015-02-13 4:46 ` Dave Taht
2015-02-13 5:13 ` Luis E. Garcia
2014-10-09 18:13 ` Dave Taht
2014-10-09 18:14 ` Sebastian Moeller
[not found] ` <54359A46.8000107@iki.fi>
2014-10-09 3:01 ` Dave Taht
2014-10-09 17:09 ` Richard Smith [this message]
[not found] ` <CABXqzy77--kb59nedBnN+cLFGftN+gnBMJ9vi_xE8niP5YHEHw@mail.gmail.com>
2014-10-09 3:23 ` 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=5436C137.8070706@gmail.com \
--to=smithbone@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@bufferbloat.net \
--cc=hannu.nyman@iki.fi \
--cc=openwrt-devel@lists.openwrt.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