From: Jonathan Morton <chromatix99@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] QoS and test setups
Date: Fri, 6 May 2016 07:41:16 +0300 [thread overview]
Message-ID: <5480FCFF-CC4C-4C72-9F5C-6BB1D55BFA0F@gmail.com> (raw)
In-Reply-To: <CALQXh-PXc=eR7mbgkCS0gGq8z578Zii0g1-jCbRnqNhoe+uDQA@mail.gmail.com>
> On 6 May, 2016, at 05:08, Aaron Wood <woody77@gmail.com> wrote:
>
> There are a LOT of assumptions made when QoS systems based on marked packets is used:
>
> - That traffic X can starve others
> - That traffic X is more/most important
Cake tries to take a more nuanced approach than the above, though it is designed for a wired link.
However, there are many systems in the wild which do implement strict priority. It is, after all, one of the easiest schemes to implement within a single transmitter unit.
- Jonathan Morton
next prev parent reply other threads:[~2016-05-06 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 2:08 Aaron Wood
2016-05-06 2:24 ` Bob McMahon
2016-05-06 4:41 ` Jonathan Morton [this message]
2016-05-07 16:50 ` Dave Taht
2016-05-07 21:49 ` Dave Taht
2016-05-08 19:07 ` Bob McMahon
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=5480FCFF-CC4C-4C72-9F5C-6BB1D55BFA0F@gmail.com \
--to=chromatix99@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=woody77@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