Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>
Subject: Re: [Cake] gaming dscp codepoint?
Date: Tue, 24 Jul 2018 17:34:29 -0700	[thread overview]
Message-ID: <CAA93jw629_i4Mx20tckUVeobeL4KWFQucjcDk_AYZbryaMe+gg@mail.gmail.com> (raw)
In-Reply-To: <22AC529F-9EF5-4ECF-85DD-F9ED08CD3C47@gmail.com>

On Tue, Jul 24, 2018 at 5:06 PM Jonathan Morton <chromatix99@gmail.com> wrote:
>
> > On 25 Jul, 2018, at 3:01 am, Dave Taht <dave.taht@gmail.com> wrote:
> >
> > cs4?
> >
> > cs4 and cs5 end up (typically) in the (oft buggy) linux vi queue on wifi.
> >
> > ef?
> >
> > do any of the gamers here observe any codepoints in use? When I
> > surveyed this a few years ago, I saw very little usage, and what
> > little there was was all over the map.
>
> If it were up to me,

Wasn't my question. Do you observe any of your games using any codepoints?

>I would use EF for realtime position/command updates and voice comms, CS0 for everything non-time-critical (like matchmaking, garage, shop), and CS1 for downloading patches.

Well, I was leaning towards cs4. I no longer remember what ef maps
into on linux wifi, particularly since qos_map_set was created for
hostapd. Is openwrt tweaking that at all?

These days my aps do not use 802.11e at all and I'm about to push a
change forcing a max of 2ms per AC via the beacon.

Clients on campus don't seem to use much dscp but I'm certainly seeing
ecn from apple devices now.


>
> Reason is, EF is the only DSCP I can count on being interpreted as "latency sensitive" rather than "for video streaming".
>
>  - Jonathan Morton
>


-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

  reply	other threads:[~2018-07-25  0:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  0:01 Dave Taht
2018-07-25  0:06 ` Jonathan Morton
2018-07-25  0:34   ` Dave Taht [this message]
2018-07-25 18:54     ` [Cake] [Make-wifi-fast] " dpreed
2018-07-25 20:13       ` Jim Gettys

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw629_i4Mx20tckUVeobeL4KWFQucjcDk_AYZbryaMe+gg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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