From: Sebastian Moeller <moeller0@gmx.de>
To: "Dave Täht" <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>,
Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Rpm] [Make-wifi-fast] VI vs BE on wifi
Date: Mon, 8 Aug 2022 19:43:32 +0200 [thread overview]
Message-ID: <FD75701C-4626-4311-AE85-504CCCAB6E85@gmx.de> (raw)
In-Reply-To: <CAA93jw5Go4tVpEXzkZ_wV0GDmE2Rbh44kWaNOWS_rLSLT6ZDqQ@mail.gmail.com>
Hi Dave,
in all fairness it depends a bit on the station AP combination how much AC_BE traffic gets hit. But essentially this graph (or rather similar graphs fro my own testing a few years back) convinced me that selecting the "L4S" DSCP to ensure mapping into AC_VI is massively misguided, to be friendly. (This also nicely illustrates the folly of https://datatracker.ietf.org/doc/html/rfc8325 Mapping Diffserv to IEEE 802.11, which does not seem to cite even a single reference showing data that the proposed scheme actually survives a contact with the existing WiFi gear in the field)...
> On Aug 8, 2022, at 19:03, Dave Taht via Make-wifi-fast <make-wifi-fast@lists.bufferbloat.net> wrote:
>
> https://forum.openwrt.org/t/reducing-multiplexing-latencies-still-further-in-wifi/133605/32
>
> If you squint, you can see what's left of the BE defaults when competing with VI
>
>
> --
> FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
> _______________________________________________
> Make-wifi-fast mailing list
> Make-wifi-fast@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/make-wifi-fast
prev parent reply other threads:[~2022-08-08 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:03 [Rpm] " Dave Taht
2022-08-08 17:43 ` Sebastian Moeller [this message]
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=FD75701C-4626-4311-AE85-504CCCAB6E85@gmx.de \
--to=moeller0@gmx.de \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=rpm@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