From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Richard Smith <smithbone@gmail.com>,
make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Testing the LEDE nbd/staging branch
Date: Mon, 29 Aug 2016 15:22:23 -0700 [thread overview]
Message-ID: <CAA93jw7h=yfr2me8BWUvcBZ5mxqGy=g_FDxQ6--qmGhudxpsbg@mail.gmail.com> (raw)
In-Reply-To: <874m639tao.fsf@toke.dk>
I have tested toke's wndr3800 build below, and with psk2+ccmp crypto
enabled, using an osx box
to drive the tests, I can get 210Mbit wifi downloads and uploads for
nearly any number of flows. Fairness is nearly perfect. w00t!
Regrettably my laptop is still running the broken code (and toke's got
patches to send), so I can't test the linux wifi on that laptop.
I(or someone with a non-borken laptop running) need to test tkip and
other forms of aes... see table here for how to configure
https://wiki.openwrt.org/doc/uci/wireless#wpa_modes
One really impressive thing, during a 24 flow download test, was how
good packet aggregation got.
Total packet count:: ideal 7702277 lookaround 4715
Average # of aggregated frames per A-MPDU: 31.8
I have never, driving tests with tcp, seen it get that good (nor have
I tested via an osx box much)
The script that I'm basically using, if you'd like to replicate my
results with your hardware/conditions with various forms of crypto on
(and please compare against off!).
#!/bin/sh
flent -t "psk2-cc-ht40-osx-ether" -H 192.168.1.201 -l 30 rrul
flent -t "psk2-cc-ht40-osx-ether" -H 192.168.1.201 -l 30 rrul_be
for i in 1 2 4 8 12 16 24;
do
flent -t "psk2-cc-ht40-$i-flows-osx-ether" -H 192.168.1.201 -l 30
--test-parameter=upload_streams=$i tcp_nup
flent -t "psk2-cc-ht40-$i-flows-osx-ether" -H 192.168.1.201 -l 30
--test-parameter=download_streams=$i tcp_ndown
done
On Mon, Aug 29, 2016 at 2:09 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Richard Smith <smithbone@gmail.com> writes:
>
>> On 08/29/2016 04:01 PM, Dave Taht wrote:
>>> I guess I'm confused - does felix's repo also have your airtime
>>> fairness scheduler?
>>
>> I may have confused you. I added the patches from your "wifi airtime fairness
>> patches could use eyeballs and testing" post to the nbd/staging branch.
>>
>> The email (indirectly) suggested that was the branch to use.
>
> Yup, that's the right thing to do.
>
> I think I managed to fix the remaining crypto bug. Will send an updated
> patch tomorrow (need to extract it from my pile of test versions). In
> the meantime, here are some images with the patch applied if someone
> wants to go ahead and test before then:
>
> https://kau.toke.dk/experiments/softq-debug/
>
> -Toke
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
http://blog.cerowrt.org
next prev parent reply other threads:[~2016-08-29 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 18:14 Richard Smith
2016-08-29 18:42 ` Toke Høiland-Jørgensen
2016-08-29 20:01 ` Dave Taht
2016-08-29 21:04 ` Richard Smith
2016-08-29 21:09 ` Toke Høiland-Jørgensen
2016-08-29 22:22 ` Dave Taht [this message]
2016-08-30 8:38 ` Richard Smith
2016-08-30 10:48 ` Toke Høiland-Jørgensen
2016-08-30 14:24 ` Richard Smith
2016-08-30 17:56 ` Toke Høiland-Jørgensen
2016-08-31 1:07 ` Richard Smith
2016-08-31 1: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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw7h=yfr2me8BWUvcBZ5mxqGy=g_FDxQ6--qmGhudxpsbg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=smithbone@gmail.com \
--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