Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: "Dave Täht" <dave@taht.net>
Cc: Cake List <cake@lists.bufferbloat.net>,
	Benjamin Cronce <bcronce@gmail.com>
Subject: Re: [Cake] Fast snack, QUIC CAKE?
Date: Thu, 17 Aug 2017 09:17:58 +0300	[thread overview]
Message-ID: <CAJq5cE3wHoxP3cw+tVS9HNRdANKPNdoP8C1+m9T7vg6fk1wBPA@mail.gmail.com> (raw)
In-Reply-To: <87shgtap86.fsf@taht.net>

[-- Attachment #1: Type: text/plain, Size: 726 bytes --]

QUIC should interact with cake in the same way as with fq_codel. Since QUIC
aims to minimise the standing queue by itself, it should usually be seen as
a "sparse" flow which cake will automatically prioritise and avoid dropping
packets from. That, of course, is what you want in a streaming protocol.

If QUIC does persistently exceed the fair share bandwidth, it'll get
signalled using ECN (if marked capable) or packet drops at a linearly
increasing frequency, just like any other protocol. I haven't studied QUIC
enough to be sure about how it reacts to that, but cake is not really
different to any other AQM in that respect. I do know that QUIC can cover a
small amount of packet loss at the receiver.

- Jonathan Morton

[-- Attachment #2: Type: text/html, Size: 803 bytes --]

      reply	other threads:[~2017-08-17  6:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09  8:36 erik.taraldsen
2017-08-11  0:16 ` Benjamin Cronce
2017-08-14 20:06   ` Dave Taht
2017-08-17  6:17     ` 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=CAJq5cE3wHoxP3cw+tVS9HNRdANKPNdoP8C1+m9T7vg6fk1wBPA@mail.gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bcronce@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave@taht.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