From: Sebastian Moeller <moeller0@gmx.de>
To: "David Fernández" <davidfdzp@gmail.com>,
"David Fernández via Starlink" <starlink@lists.bufferbloat.net>,
starlink@lists.bufferbloat.net
Subject: Re: [Starlink] [Rpm] Fwd: [Make-wifi-fast] make-wifi-fast
Date: Wed, 21 Dec 2022 08:54:22 +0100 [thread overview]
Message-ID: <5F7B7DE2-D356-4183-9DC9-EF80BF83E660@gmx.de> (raw)
In-Reply-To: <CAC=tZ0pKLeM=7xsK_d6aL6R467zFiRFf18_hXLLzvP4PCdoqpQ@mail.gmail.com>
Hi,
See [SM] below.
On 21 December 2022 08:37:27 CET, "David Fernández via Starlink" <starlink@lists.bufferbloat.net> wrote:
>What about this?
>https://www.wi-fi.org/discover-wi-fi/wi-fi-certified-wmm-programs
>
>Isn't this Wi-Fi MM (Multimedia) supposed to solve Wi-Fi QoS issues?
[SM] In home network reality it failed to do so. I would guess partly because the admission control component is optional and as far as I can tell not available in the usual WiFi routers and APs. A free for all priority system that in addition diminishes the total achievable throughput when the higher priority tiers are used introduces at least as much QoS issues a it solves IMHO. This might be different for 'enterprise WiFi gear' but I have no experience with that...
Regard
Sebastian
P.S.: This feels like you might responded to a different thread then the iperf2 one we are in right now?
>
>> Date: Thu, 08 Dec 2022 11:04:13 -0800
>> From: rjmcmahon <rjmcmahon@rjmcmahon.com>
>> To: Sebastian Moeller <moeller0@gmx.de>
>> Cc: rjmcmahon via Make-wifi-fast
>> <make-wifi-fast@lists.bufferbloat.net>, Dave Täht
>> <dave.taht@gmail.com>, Rpm <rpm@lists.bufferbloat.net>, libreqos
>> <libreqos@lists.bufferbloat.net>, Dave Taht via Starlink
>> <starlink@lists.bufferbloat.net>, bloat <bloat@lists.bufferbloat.net>
>> Subject: Re: [Starlink] [Rpm] Fwd: [Make-wifi-fast] make-wifi-fast
>> 2016 & crusader
>> Message-ID: <4e8ee21b1a69fba9c61366f6055fbc13@rjmcmahon.com>
>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>
>> Thanks for the well-written response Sebastian. I need to think more
>> about the load vs no load OWD differentials and maybe offer that as an
>> integrated test. Thanks for bringing it up (again.) I do think a
>> low-duty cycle bounceback test to the AP could be interesting too.
>>
>> I don't know of any projects working on iperf 2 & containers but it has
>> been suggested as useful.
>>
>> Bob
>>
>_______________________________________________
>Starlink mailing list
>Starlink@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/starlink
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2022-12-21 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 7:37 David Fernández
2022-12-21 7:54 ` Sebastian Moeller [this message]
2022-12-23 15:02 ` David Fernández
2022-12-24 0:00 David P. Reed
2023-01-02 17:35 David Fernández
2023-01-02 18:44 ` Ben Greear
2023-01-02 18:57 ` Dave Collier-Brown
2023-01-02 19:00 ` Sebastian Moeller
2023-01-03 7:44 ` David Fernández
2023-01-03 8:18 ` Sebastian Moeller
2023-01-02 19:14 ` Dave Taht
2023-01-03 9:00 ` David Fernández
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/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5F7B7DE2-D356-4183-9DC9-EF80BF83E660@gmx.de \
--to=moeller0@gmx.de \
--cc=davidfdzp@gmail.com \
--cc=starlink@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