Lets make wifi fast again!
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: make-wifi-fast@lists.bufferbloat.net, cake@lists.bufferbloat.net
Subject: [Make-wifi-fast] Flent results for point-to-point Wi-Fi on LEDE/OM2P-HS available
Date: Mon, 30 Jan 2017 22:21:31 +0100	[thread overview]
Message-ID: <32C42951-373F-4D90-8936-AA07039E5D73@gmail.com> (raw)

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

Hi, I’ve posted some Flent results and analysis for point-to-point Wi-Fi using LEDE on OM2P-HS (ath9k):

http://www.drhleny.cz/bufferbloat/wifi_bufferbloat.html <http://www.drhleny.cz/bufferbloat/wifi_bufferbloat.html>

Over 500 runs were done using different configurations, as the effects of various changes were explored. In case someone has the time to respond, there are a number of questions in red. Whatever feedback I get I’ll try to incorporate into a final document. Also, if I’ve made any false assertions I’d love to hear about it.

As described on the page, I’m doing this to try to help my cooperative WISP here in Czech, and also in case it helps the Bufferbloat project somehow. Although much of the new Wi-Fi work is occurring at the driver level, I hope it’s not misguided to still explore using the qdisc layer for Wi-Fi, particularly in cases where a new Wi-Fi driver can’t be deployed.

These first results are from LEDE on the OM2P-HS, but I hope to get some test devices from my WISP soon to test the hardware they’re using (Ubiquiti Wi-Fi devices with custom Voyage Linux routers running on a PCengines APU).

Regards,
Pete


[-- Attachment #2: Type: text/html, Size: 1706 bytes --]

             reply	other threads:[~2017-01-30 21:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 21:21 Pete Heist [this message]
2017-01-30 21:44 ` 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
2017-02-16  7:57         ` Pete Heist
2017-02-16  8:42           ` [Make-wifi-fast] [Cake] " 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       ` [Make-wifi-fast] " 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             ` [Make-wifi-fast] [Cake] " John Yates
2017-01-30 23:55 ` [Make-wifi-fast] " 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/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=32C42951-373F-4D90-8936-AA07039E5D73@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --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