From: Jonathan Morton <chromatix99@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] New to cake. Some questions
Date: Fri, 10 Jun 2016 01:17:14 +0300 [thread overview]
Message-ID: <C202E25A-5CB8-46F8-A1FC-9EAB9370078D@gmail.com> (raw)
In-Reply-To: <5759E14D.1050806@darbyshire-bryant.me.uk>
> On 10 Jun, 2016, at 00:36, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
>
>> 5. Is there still the udp packet dropping problem? e.g. games that are using udp.
>> If yes does it make sense to apply diffserv classes manually? How to do this?
> What udp packet problem?
He’s probably referring to the tendency of non-flow-isolating AQMs to drop packets indiscriminately when under load.
Cake is flow-isolating and thus applies a separate AQM algorithm to each flow. As such, UDP gaming/VoIP traffic won’t get dropped unless it exceeds its fair share of the link, which is unlikely for a well-designed, lightweight protocol.
We really should make an effort to put a more intuitive GUI interface on this. These questions indicate a user overwhelmed by many options without guidance.
- Jonathan Morton
next prev parent reply other threads:[~2016-06-09 22:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 20:58 Dennis Fedtke
2016-06-09 21:30 ` moeller0
2016-06-09 22:45 ` Dennis Fedtke
2016-06-09 23:11 ` moeller0
2016-06-10 0:41 ` Dennis Fedtke
2016-06-10 5:16 ` moeller0
2016-06-10 0:49 ` Dennis Fedtke
2016-06-10 5:20 ` moeller0
2016-06-10 12:43 ` Dennis Fedtke
2016-06-10 13:02 ` moeller0
2016-06-10 14:05 ` Dennis Fedtke
2016-06-10 14:26 ` Sebastian Moeller
2016-06-10 22:01 ` Benjamin Cronce
2016-06-09 21:36 ` Kevin Darbyshire-Bryant
2016-06-09 22:17 ` Jonathan Morton [this message]
2016-06-09 22:49 ` moeller0
2016-06-09 23:27 ` Jonathan Morton
2016-06-10 8:19 ` moeller0
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=C202E25A-5CB8-46F8-A1FC-9EAB9370078D@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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