From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Managed to break 802.11n (on a 3800)
Date: Sun, 19 Jan 2014 22:12:13 +0100 [thread overview]
Message-ID: <CAA6266F-D040-4155-9CEC-EBFC93709793@gmx.de> (raw)
In-Reply-To: <87lhyb3czm.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 2462 bytes --]
Hi Toke,
On Jan 19, 2014, at 21:58 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Sebastian Moeller <moeller0@gmx.de> writes:
>
>> I noticed the new "hostnames are mandatory police" kick in:
>
> Right, botched that; should be fixed properly now.
That was fast, and:
bash-3.2$ ./netperf-wrapper --list-tests
Available tests:
cisco_5tcpup : RTT Fair Realtime Response Under Load
cisco_5tcpup_2udpflood : Cisco 5TCP up + 2 6Mbit UDP
cubic_ledbat_1 : Cubic vs LEDBAT upload streams w/ping
ledbat_cubic_1 : Cubic vs LEDBAT upload streams w/ping
ping : Straight ping test
reno_cubic_westwood_ledbat : Realtime Response Under Load
(with different congestion control algs)
reno_cubic_westwood_lp : Realtime Response Under Load
(with different congestion control algs)
rrul : Realtime Response Under Load
rrul46 : Realtime Response Under Load - Mixed IPv4/6
rrul46compete : Realtime Response Under Load - Mixed v4/v6 compete
rrul_be : Realtime Response Under Load - exclusively Best Effort
rrul_noclassification : Realtime Response Under Load - no classification on data flows
rtt_fair : RTT Fair Realtime Response Under Load
rtt_fair4be : RTT Fair Realtime Response Under Load
rtt_fair6be : RTT Fair Realtime Response Under Load
tcp_1down : Bidirectional TCP streams w/ping
tcp_1up : Single TCP upload stream w/ping
tcp_bidirectional : Bidirectional TCP streams w/ping
tcp_download : TCP download stream w/ping
tcp_upload : TCP upload stream w/ping
udp_flood : UDP flood w/ping
bash-3.2$
Thanks a lot.
>
>> Wireless is weird...
>
> Yes, wayy too much black magic involved…
What I failed to mention, testing against demo (~32ms unloaded ping RTT) from home gives ping RTT around 50ms, from the university 200ms (both with tcp_bidirectional). Ouch, and this with a massive rsync job running at home on a wired machine(over the atlantic, so sharing resources with tcp_bidirectional).
Dave, you are right default wireless performance truly is suboptimal…
best
Sebastian
>
> -Toke
[-- Attachment #2.1: Type: text/html, Size: 4887 bytes --]
[-- Attachment #2.2: tcp_bidirectional_EKUT.png --]
[-- Type: image/png, Size: 47722 bytes --]
[-- Attachment #2.3: tcp_bidirectional_HOME2DEMO.png --]
[-- Type: image/png, Size: 51837 bytes --]
next prev parent reply other threads:[~2014-01-19 21:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 15:03 Aaron Wood
2014-01-16 15:29 ` Sebastian Moeller
2014-01-16 15:46 ` Aaron Wood
2014-01-16 17:20 ` Sebastian Moeller
2014-01-16 19:08 ` Aaron Wood
2014-01-16 20:10 ` Sebastian Moeller
2014-01-16 21:33 ` Aaron Wood
2014-01-16 22:50 ` Dave Taht
2014-01-16 23:15 ` Sebastian Moeller
2014-01-16 23:40 ` Dave Taht
2014-01-17 20:15 ` Toke Høiland-Jørgensen
2014-01-17 20:17 ` Dave Taht
2014-01-19 19:01 ` Toke Høiland-Jørgensen
2014-01-19 20:01 ` Sebastian Moeller
2014-01-19 20:58 ` Toke Høiland-Jørgensen
2014-01-19 21:12 ` Sebastian Moeller [this message]
2014-01-16 22:35 ` Dave Taht
2014-01-16 22:30 ` Dave Taht
2014-01-16 22:56 ` Sebastian Moeller
2014-01-16 23:12 ` Dave Taht
2014-01-16 23:25 ` Sebastian Moeller
2014-01-16 15:38 ` Robert Bradley
2014-01-16 15:46 ` Aaron Wood
2014-01-16 22:08 ` 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=CAA6266F-D040-4155-9CEC-EBFC93709793@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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