From: Loganaden Velvindron <loganaden@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] crypto-fq bug postmortem is up
Date: Sat, 17 Sep 2016 21:26:04 +0400 [thread overview]
Message-ID: <CAOp4FwS6yG-mQcgVtw+GazDW9hzE-uMo9T1=zjq8xa6wy1HeQQ@mail.gmail.com> (raw)
In-Reply-To: <CAOp4FwSR_tgbE8j8Fm9NKPYrqqx1nGDY8rP3OpJoJrO8Jweb-g@mail.gmail.com>
On Sat, Sep 17, 2016 at 9:12 PM, Loganaden Velvindron
<loganaden@gmail.com> wrote:
> On Sat, Sep 17, 2016 at 1:42 AM, Dave Taht <dave.taht@gmail.com> wrote:
>> at:
>>
>> http://blog.cerowrt.org/post/crypto_fq_bug/
>>
>> I am very interested to try to remember more of the suggestions, and
>> blind alleys, and why we thought they were possibilities... and draw
>> more conclusions as to what we did right, and wrong.
>>
>> Please comment, and send links.
>>
>> If I have more time, I'll make it shorter. Or funnier. And add more
>> pictures, captures, and links. Finding this bug *eventually* got to be
>> fun.
>>
>
> My home network:
>
> FTTH modem (bridge) --- tp-link archer c7
> (pppoe+sqm+simple_pppoe(fq_codel)+ap) ---- (lan cable) --- tp-link
> archer c7 v2 with the experimental firmware(ap):
> Quick and dirty test:
>
> on non-patched openwrt wifi(wpa-psk):
> https://www.dslreports.com/speedtest/5028614
>
> on tp-link archer c7 v2 with toke's firmware(wpa-psk):
> https://www.dslreports.com/speedtest/5028349
>
> My brother said that "It feels like ethernet both in terms of
> throughput and latency". My brother is hammering the the tp-link
> archer c7 box with bittorrent, whatsapp, viber, and normal http.
Testing on my android smartphone (android 6.0.1):
Unpatched ap:
https://www.dslreports.com/speedtest/5028965
Patched ap:
https://www.dslreports.com/speedtest/5028940
On smartphones, it looks like you can get better throughput with
toke's firmware.
next prev parent reply other threads:[~2016-09-17 17:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 21:42 Dave Taht
2016-09-17 8:33 ` Loganaden Velvindron
2016-09-17 17:12 ` Loganaden Velvindron
2016-09-17 17:26 ` Loganaden Velvindron [this message]
2016-09-17 17:33 ` Dave Taht
2016-09-17 17:35 ` Toke Høiland-Jørgensen
2016-09-17 17:50 ` Loganaden Velvindron
2016-09-18 5:39 ` Loganaden Velvindron
2016-09-18 6:19 ` Dave Taht
2016-09-18 6:27 ` Loganaden Velvindron
2016-09-18 14:24 ` Loganaden Velvindron
2016-09-18 20:50 ` Sebastian Moeller
2016-09-19 3:56 ` Loganaden Velvindron
2016-09-19 8:33 ` moeller0
2016-09-19 11:27 ` Toke Høiland-Jørgensen
2016-09-19 11:36 ` moeller0
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='CAOp4FwS6yG-mQcgVtw+GazDW9hzE-uMo9T1=zjq8xa6wy1HeQQ@mail.gmail.com' \
--to=loganaden@gmail.com \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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