From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] testing cake at 55mbit down/5mbit up
Date: Thu, 7 May 2015 02:48:49 +0300 [thread overview]
Message-ID: <6FFE3A76-B4DD-4567-8B4C-AFEE6CA913CB@gmail.com> (raw)
In-Reply-To: <CAA93jw5F28YuQxx0pxYjQYPtuHxSsB7kY8t5_Kr1yJR7LX3uQw@mail.gmail.com>
> On 5 May, 2015, at 22:43, Dave Taht <dave.taht@gmail.com> wrote:
>
> the diffserv4 thing did not line
> up with the markings netperf-wrapper is using for the rrul test.
True, but neither does Wi-Fi QoS, which ignores the low-order DSCP bits and uses only the Precedence ones, with some re-ordering:
Precedence 0 & 3 go into BE,
1 & 2 into BK,
4 & 5 into VI,
6 & 7 into VO.
Both CS5 and EF therefore fall into the VI (video) queue on Wi-Fi; only CS6 and above get the VO (voice) queue. This doesn’t make much sense, which is probably one reason why I ignored that practice when setting up cake.
With cake, CS5 and EF both fall into the "voice" class; CS5 supposedly corresponds to “voice signalling”, which is why I put it there. Cake’s “video” class is meant for applications which need reliable access to bandwidth (eg. streaming video) rather than especially low latency.
Here’s a summary of where all the well-known DSCPs end up on Wi-Fi and cake:
DSCP WiFi Cake
==== ==== ====
CS0 BE BE <- default
TOS1 BE VI <- max reliability (legacy)
TOS2 BE BE <- max throughput (legacy)
TOS4 BE VI <- min delay (legacy)
CS1 BK BK <- low priority
AF1x BK BE <- high throughput
CS2 BK VI <- admin & management
AF2x BK VI <- low latency data, ie. database
CS3 BE VI <- broadcast video
AF3x BE VI <- multimedia streaming, ie. YouTube
CS4 VI VO <- realtime interactive, ie. games
AF4x VI VI <- multimedia conferencing
CS5 VI VO <- signalling
VA VI VO <- telephony with capacity reservation
EF VI VO <- VoIP and games
CS6 VO VO <- network control, ie. NTP
CS7 VO VO <- network control, ie. routing
- Jonathan Morton
prev parent reply other threads:[~2015-05-06 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 19:43 Dave Taht
2015-05-05 19:56 ` Dave Taht
2015-05-05 20:17 ` Dave Taht
2015-05-06 23:48 ` Jonathan Morton [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/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=6FFE3A76-B4DD-4567-8B4C-AFEE6CA913CB@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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