Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Adrian Popescu <adriannnpopescu@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] CAKE set-associative hashing
Date: Sun, 29 Oct 2017 17:38:38 +0200	[thread overview]
Message-ID: <CAF3M4P3mxVrZaFu0kh6s3cGZtgxwqz-yg0KPCjh9iX99Z18cPg@mail.gmail.com> (raw)
In-Reply-To: <CAJq5cE01YYPBTvZnDJxaktnZyRFJqRXu5njsT8nZkbxj8LofGQ@mail.gmail.com>

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

Thank you Jonathan. I'm going over the code to learn more about CAKE. This
set-associative hashing seems to be pretty useful. I'll ask more questions
about the code as I try to understand it better.

On Sun, Oct 29, 2017 at 12:14 PM, Jonathan Morton <chromatix99@gmail.com>
wrote:

> Yes, in the same way as is caused by SFQ's periodic hash perturbation.
>
> However, in Cake this is a rare condition brought on by exceptional load;
> it typically takes hundreds of bulk flows to get an unresolvable
> collision.  The use of AQM also means that the extent of reordering is
> reduced due to shorter average queues.  Most sane protocols, including
> TCP-SACK, should cope fine.
>
> - Jonathan Morton
>

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

  reply	other threads:[~2017-10-29 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29 10:07 Adrian Popescu
2017-10-29 10:14 ` Jonathan Morton
2017-10-29 15:38   ` Adrian Popescu [this message]
2017-10-29 22:20     ` Dave Taht
2017-10-29 22:39       ` Jonathan Morton

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=CAF3M4P3mxVrZaFu0kh6s3cGZtgxwqz-yg0KPCjh9iX99Z18cPg@mail.gmail.com \
    --to=adriannnpopescu@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@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