From: "Richard A. Smith" <richard@laptop.org>
To: Sebastian Moeller <moeller0@gmx.de>, Alpha Sparc <alphasparc@gmail.com>
Cc: openwrt-devel <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: Mon, 06 Oct 2014 12:02:46 -0400 [thread overview]
Message-ID: <5432BD26.1070907@laptop.org> (raw)
In-Reply-To: <2BFE70BD-92CC-4639-8B3C-15EBA32A20A9@gmx.de>
On 10/02/2014 10:05 AM, Sebastian Moeller wrote:
> I assume you are talking about the pure routing performance with no firewall/NAT and traffic-shaping involved? I think they pretty much are equal (pretty much the same kernel and most of the cerowrt guts are from openwrt bb trunk). But I have not tested that (I have only one cerowrt/openwrt capable router and that pretty much is my main router).
> If you are talking about comparing QOS-scripts with SQM-scripts, they also seem to top out at roughly 50-60 Mbps (down- and uplink combined), it seems hfsc (qos-scripts) and HTB (sam-scripts) are equally expensive on MIPS.
> Now if you are setup to do tests yourself I would love to hear the results. I would be happy to help you getting SQM-scripts to work (so far all people interested disappeared before or just after sharing initial test results).
Do you still need testers? I have a bit of an interest here.
I have spare routers that I can run OpenWRT or CeroWRt on and I'm setup
to test with netperf, netperf-wrapper on my local network
( desktop -> router -> laptop ) it's Gbit so I can easily saturate
the router.
What I don't have is a lot of time but I can do a few runs in the
evenings or on weekends. I also am very out of touch with the latest
and greatest QoS vs SQM development and configuration so you will have
to feed me test recipes.
--
Richard A. Smith <richard@laptop.org>
Former One Laptop per Child
next prev parent reply other threads:[~2014-10-06 16:02 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 [this message]
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
[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=5432BD26.1070907@laptop.org \
--to=richard@laptop.org \
--cc=alphasparc@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
--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