From: Dave Taht <dave@taht.net>
To: Pete Heist <pete@heistp.net>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Make-wifi-fast] Ubiquiti fixed framing experience
Date: Tue, 22 Jan 2019 12:06:18 -0800 [thread overview]
Message-ID: <87zhrsjw3p.fsf@taht.net> (raw)
In-Reply-To: <B91A1F93-B1A6-44BE-950F-4C0D5C0CB335@heistp.net> (Pete Heist's message of "Tue, 22 Jan 2019 11:09:57 +0100")
Pete Heist <pete@heistp.net> writes:
>> On Jan 22, 2019, at 10:08 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>
>> Pete Heist <pete@heistp.net> writes:
>>
>>> Anyway that’s my story, it’s 2019 and it seems that vendors are still
>>> not thinking about what latency means, even when it can start to
>>> affect TCP...
>>
>> Nice writeup. Have you considered writing a blog post? :)
>
> I’ll try to do this together with more practical stories about queueing the backhaul.
>
> How airtime is managed is a serious thing. It’s like WiFi gold, but I probably don’t have to mention that on this list. :)
Also your
https://community.ubnt.com/t5/airMAX-AC/New-Flexible-framing-and-huge-improvements-in-TCP-latency/td-p/2385132
reference pointed at preseem which is a company started to better manage
wifi (with tools like that - and means to put fq_codel/htb/cake etc
inline) Go, preseem!
>
> 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:[~2019-01-22 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 8:50 Pete Heist
2019-01-22 9:08 ` Toke Høiland-Jørgensen
2019-01-22 10:09 ` Pete Heist
2019-01-22 20:06 ` Dave Taht [this message]
2019-01-22 21:06 ` Pete Heist
2019-01-22 20:04 ` 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=87zhrsjw3p.fsf@taht.net \
--to=dave@taht.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=pete@heistp.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