Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Török Edwin" <edwin@etorok.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-9 released
Date: Tue, 18 Mar 2014 17:22:16 +0200	[thread overview]
Message-ID: <532864A8.2030404@etorok.net> (raw)
In-Reply-To: <CAA93jw6m+uN99RqYX2mmGT9jRW85ZSdvo2jokq+S5YyKbYkiZA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

On 03/18/2014 04:21 PM, Dave Taht wrote:
> Regrettably the SQM system on the wndr series of hardware maxes out on
> CPU at about 50Mbit down, 10Mbit up, or any combination thereof (e.g
> 25/25 works). If you want to apply this code at higher rates, routing
> hardware with more "oomph" is needed.
> 
> I would be interested in a rrul test of your 50Mbit system. My tests
> of verizon at 25/25 showed them well managed on the up, far less well
> managed on the down, so in your 50Mbit design you might want to merely
> control the down with SQM.

Host: Linux 3.14-rc5, AMD FX(tm)-8350 Eight-Core Processor, cpufreq set to performance, cpb disabled
Router: NETGEAR WNDR3700v2, 3.10.32-9
Target: OpenBSD 5.4, QEMU Virtual CPU version (cpu64-rhel6), 3300.54 MHz

Host <-> Router connected via gigabit ethernet.

I confirmed that my target can do >50Mbit to another server, netperf shows 128*10^6 bit/s / 108 * 10^6 bit/s.

SQM with link-layer none settings:
 * download speed: 46000 kbit/s, upload speed 50000 kbit/s (~95% of measured speed on ISP's speedtest site).
 * fq_codel (default)
 * simple.qos
 * link-layer: none
 * results: <sqm_on_none.png>

SQM off: <sqm_off.png>

SQM with overhead Ethernet overhead 30: <sqm-on-30.png>
SQM with overhead Ethernet overhead 22: <sqm-on-22.png>

Should I also run a rrul46/rrul46compete test?

Best regards,
--Edwin

[-- Attachment #2: sqm_on_22.png --]
[-- Type: image/png, Size: 266647 bytes --]

[-- Attachment #3: sqm_on_30.png --]
[-- Type: image/png, Size: 257373 bytes --]

[-- Attachment #4: sqm_on_none.png --]
[-- Type: image/png, Size: 253387 bytes --]

[-- Attachment #5: sqm_off.png --]
[-- Type: image/png, Size: 242595 bytes --]

  reply	other threads:[~2014-03-18 15:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 19:58 Dave Taht
2014-03-16 21:27 ` Valdis.Kletnieks
2014-03-16 21:45   ` Dave Taht
2014-03-17  0:03     ` Toke Høiland-Jørgensen
2014-03-17  0:42     ` Valdis.Kletnieks
2014-03-17  0:54       ` Dave Taht
2014-03-17 12:20 ` Michael Richardson
2014-03-17 13:40   ` Dave Taht
2014-03-17 14:30     ` Toke Høiland-Jørgensen
2014-03-17 14:39       ` Toke Høiland-Jørgensen
2014-03-17 14:55       ` Dave Taht
2014-03-17 14:55     ` Michael Richardson
2014-03-17 15:18       ` Dave Taht
2014-03-18 10:00 ` Török Edwin
2014-03-18 12:12   ` Sebastian Moeller
2014-03-18 14:21     ` Dave Taht
2014-03-18 15:22       ` Török Edwin [this message]
2014-03-18 15:35         ` Dave Taht
2014-03-18 16:49           ` Török Edwin
2014-03-18 17:03             ` Dave Taht
2014-03-18 17:06           ` Valdis.Kletnieks

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=532864A8.2030404@etorok.net \
    --to=edwin@etorok.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@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