Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "Björn Grönvall" <bjorngx@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] and the bad cpu news on arm is
Date: Tue, 22 Dec 2015 06:42:24 +0200	[thread overview]
Message-ID: <B160812B-FD61-489A-8564-E18003D5FC1C@gmail.com> (raw)
In-Reply-To: <CAA93jw6wqb5Kw6wk4+XvzNTbJPM4WjsEzFt=E5YiJ90c_MA2Nw@mail.gmail.com>


> On 20 Dec, 2015, at 14:59, Dave Taht <dave.taht@gmail.com> wrote:
> 
> I do happen to like the set associativity idea, but it's proving
> really hard to show its value with any existing tests we have.

Actually, your little experiment with dual-isolation inadvertently showed how robust the set-associative hash is.  Despite being effectively reduced to an 8-queue system (between a single pair of hosts), it was still able to keep four TCP ack flows, four UDP probe flows and a ping flow effectively separate from four TCP bulk flows, to the point where you couldn’t distinguish it from a properly functioning version of Cake under the same load.  Try *that* with a plain, collision-prone hash function.

 - Jonathan Morton


  parent reply	other threads:[~2015-12-22  4:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 20:03 Dave Taht
2015-12-20  8:55 ` Björn Grönvall
2015-12-20 12:59   ` Dave Taht
2015-12-22  0:30     ` Jonathan Morton
2015-12-22  4:42     ` Jonathan Morton [this message]
2015-12-22  0:31   ` 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=B160812B-FD61-489A-8564-E18003D5FC1C@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=bjorngx@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