Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net,
	 Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Subject: Re: [Cake] cake dual hash for dualdst, dualsrc
Date: Tue, 22 Dec 2015 13:29:30 +0100	[thread overview]
Message-ID: <CAA93jw4CubeedX=e+qLO=r=WZs91ueoCX+qDLKz9KZebx_bVzw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6QDV9eRSyiD9twvvMrib4O7Bi0hAWLm-ZmLsX7bGFNyg@mail.gmail.com>

It turns out that I actually proved something slightly different -
cake's current codel implementation doesn't work worth a damn.

Which I already "knew" from other test runs against other data sets.

Toke's 2mbit/384k dataset arrived this morning, more or less making
that obvious.

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 14:57 Dave Taht
2015-12-21 15:05 ` Jonathan Morton
     [not found]   ` <877fk7lts4.fsf@toke.dk>
2015-12-21 16:06     ` Jonathan Morton
2015-12-21 15:06 ` Loganaden Velvindron
2015-12-21 15:54 ` moeller0
2015-12-22 12:29 ` Dave Taht [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='CAA93jw4CubeedX=e+qLO=r=WZs91ueoCX+qDLKz9KZebx_bVzw@mail.gmail.com' \
    --to=dave.taht@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