From: Jon Pike <jonpike54@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Upcoming WiFi standard to set per-flow DSCP values?
Date: Tue, 4 Jan 2022 15:57:53 -0800 [thread overview]
Message-ID: <CALukJKQf+FSnW55Tmva__HdWPNjkhwV9dwwr4XDj77JtokUxCA@mail.gmail.com> (raw)
In-Reply-To: <87r19nb27v.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
Heh... So each and everyone in the stadium can have ALL their data
prioritized above everybody else's! For a more Egalitarian world!
Sigh... Meanwhile, back in reality...
An aside, is that commit in git a significant improvement on the mappings,
or just some minor tweaks?
Jon
On Tue, Jan 4, 2022, 1:49 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Jon Pike <jonpike54@gmail.com> writes:
>
> > Might it have to do with these RFC's?
> >
> >
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=a5e3def1822431ef6436cb493df77006dbacafd6
>
> Don't think so; that's just the standard static mapping. Bob pointed me
> to this:
>
>
[-- Attachment #2: Type: text/html, Size: 1332 bytes --]
next prev parent reply other threads:[~2022-01-04 23:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1641315601.32049.make-wifi-fast@lists.bufferbloat.net>
2022-01-04 18:31 ` Jon Pike
2022-01-04 21:49 ` Toke Høiland-Jørgensen
2022-01-04 23:57 ` Jon Pike [this message]
2022-01-05 12:02 ` Toke Høiland-Jørgensen
2022-01-05 12:28 ` Sebastian Moeller
2022-01-05 17:11 ` Aaron Wood
2022-01-05 18:33 ` Sebastian Moeller
2022-01-05 20:42 ` Bob McMahon
2022-01-09 22:51 ` Sebastian Moeller
2022-01-09 23:41 ` Dave Taht
2022-01-10 16:02 ` Bob McMahon
[not found] <mailman.1399.1641415377.1267.make-wifi-fast@lists.bufferbloat.net>
2022-01-07 5:48 ` Jon Pike
2022-01-03 21:06 Toke Høiland-Jørgensen
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=CALukJKQf+FSnW55Tmva__HdWPNjkhwV9dwwr4XDj77JtokUxCA@mail.gmail.com \
--to=jonpike54@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.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