Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Pete Heist <peteheist@gmail.com>
Cc: Dave Taht <dave@taht.net>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake flenter results round 4
Date: Tue, 5 Dec 2017 09:10:28 -0800	[thread overview]
Message-ID: <CAA93jw75JCrr91-Fu5t6L3BoDfQW9WcCBKD9NVE6hWXU5h26fA@mail.gmail.com> (raw)
In-Reply-To: <22F038E2-3A67-457D-8B3A-18AE82B6FAF4@gmail.com>

On Mon, Dec 4, 2017 at 1:02 AM, Pete Heist <peteheist@gmail.com> wrote:
>
> On Dec 4, 2017, at 4:29 AM, Dave Taht <dave@taht.net> wrote:
>
>
> *** Round 5 Plans
>
> * If I do another high RTT test, make rtt 1000ms default and try even higher
>
> * From Dave: tcp bbr, cdg, reno? dctcp would be weirdly interesting.
>
> * From Dave: slot 4ms 4ms bytes 10k 16
>
> * If I get time I could change flenter to do asymmetric bandwidth tests and
> go
> back to Dave’s four box config with ingress cake, which would probably be a
> more
> common config. All depends on time available…
>
>
> Well, let's see what happens on netdev.
>
> I took a few steps towards ripping out blue for comparison the other
> day.
>
>
> Ok, irtt needs shoring up before its first “pre-release release”, likely to
> be in mid-December. I’ll focus on that with what time I have (which is less
> now until the new year) until more is known.
>
> I think we can say Cake is stable and helps in many situations over what’s
> currently available. There are smaller mysteries in different corners, but
> they usually come down to something like:
>
> - the queue has been lost
> - it's configured wrong
> - that’s how it should be
> - the device or driver isn’t working right
> - the device is multi-queue
> - the cpu is over-taxed
> - the timer resolution isn’t high enough
>
> Maybe we can make these deployment issues easier for people to deal with
> over time, first through documentation, then proposing and implementing
> solutions if they become clear. Overall though, I’m glad Cake is available,
> because in many situations people can just add a few keywords and enjoy the
> benefits…

"sch_cake cookbook"
>
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>



-- 

Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619

      reply	other threads:[~2017-12-05 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-02 20:13 Pete Heist
     [not found] ` <CAJq5cE1rcgTY0wd8wK3p8XmHpiQ01ja3k+NNdjXtrpSm45hGEA@mail.gmail.com>
2017-12-02 21:15   ` Jonathan Morton
2017-12-03  8:28     ` Pete Heist
2017-12-04  3:29 ` Dave Taht
2017-12-04  9:02   ` Pete Heist
2017-12-05 17:10     ` 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=CAA93jw75JCrr91-Fu5t6L3BoDfQW9WcCBKD9NVE6hWXU5h26fA@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave@taht.net \
    --cc=peteheist@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