From: "Dave Täht" <dave@taht.net>
To: Pete Heist <peteheist@gmail.com>, Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net, make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Cake] [Make-wifi-fast] Flent results for point-to-point Wi-Fi on LEDE/OM2P-HS available
Date: Wed, 15 Feb 2017 15:03:43 -0800 [thread overview]
Message-ID: <d2f998f1-2955-2aae-2286-38807dede5f2@taht.net> (raw)
In-Reply-To: <42AC44CD-8C22-4EBC-B6AB-7786BA505D07@gmail.com>
On 2/14/17 12:56 AM, Pete Heist wrote:
>
>> On Jan 31, 2017, at 12:21 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> It would be my hope that 802.11e is off (rrul will show this, and we
>> still do badly with it on)
>
> Does this mean to try disabling WMM (uci set wireless.default_radio0.wmm='0’)?
>
> That’s how I took it, as it looks like WMM is a subset of 802.11e. But if I do that, I lose 802.11n support and throughput drops from ~90 Mbps to ~22 Mbps. I could get those results out of interest, but it wouldn’t be practical in the field.
>
> Or is there another way to turn off 802.11e without losing 802.11n support?
you are correct. I misspoke. turning off wmm disables 802.11n. Which I'd
forgotten until I too ran a test with wmm disabled a week or two back.
What I'd done in cerowrt was disable the internal mac80211 QoS
classifier entirely. (-1 line of code). Another way to do it is to apply
an iptables rule to wash away all diffserv markings, but I don't care
for that answer.
try as I might I cannot remember if this was even possible in hostapd or
in the mac layer any other way. I'll look this week.
> Pete
>
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
next prev parent reply other threads:[~2017-02-15 23:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 21:21 [Cake] " Pete Heist
2017-01-30 21:44 ` [Cake] [Make-wifi-fast] " Toke Høiland-Jørgensen
2017-01-30 22:48 ` Aaron Wood
2017-02-01 14:53 ` Toke Høiland-Jørgensen
2017-01-30 23:21 ` Dave Taht
2017-01-31 16:40 ` Pete Heist
2017-02-14 8:56 ` Pete Heist
2017-02-15 23:03 ` Dave Täht [this message]
2017-02-16 7:57 ` Pete Heist
2017-02-16 8:42 ` Sebastian Moeller
2017-02-16 9:17 ` Pete Heist
2017-02-16 16:15 ` Aaron Wood
2017-02-16 16:21 ` Sebastian Moeller
2017-02-16 16:51 ` Pete Heist
2017-02-16 17:19 ` Jonathan Morton
2017-02-16 19:05 ` Pete Heist
2017-02-16 20:54 ` Pete Heist
2017-02-16 21:03 ` Sebastian Moeller
2017-02-17 7:53 ` Pete Heist
2017-02-17 9:52 ` Toke Høiland-Jørgensen
2017-02-19 15:25 ` Dave Taht
2017-01-31 15:52 ` Pete Heist
2017-02-01 14:48 ` Toke Høiland-Jørgensen
2017-02-02 8:25 ` Pete Heist
2017-02-07 11:57 ` Toke Høiland-Jørgensen
2017-02-08 15:26 ` Pete Heist
2017-02-08 16:11 ` Toke Høiland-Jørgensen
2017-02-08 16:35 ` Dave Taht
2017-02-08 17:10 ` Dave Taht
2017-02-08 17:11 ` Dave Taht
2017-02-09 8:35 ` Pete Heist
2017-02-09 7:45 ` Pete Heist
2017-02-09 13:51 ` Toke Høiland-Jørgensen
2017-02-09 14:20 ` Pete Heist
2017-02-09 14:44 ` Toke Høiland-Jørgensen
2017-02-10 7:51 ` Pete Heist
2017-02-08 18:29 ` John Yates
2017-01-30 23:55 ` Dave Taht
2017-01-31 16:58 ` Pete Heist
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2f998f1-2955-2aae-2286-38807dede5f2@taht.net \
--to=dave@taht.net \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=peteheist@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