Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Loganaden Velvindron <loganaden@gmail.com>
Cc: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>,
	Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] man page bikeshed
Date: Mon, 30 Jul 2018 10:39:51 -0700	[thread overview]
Message-ID: <CAA93jw6Q8otP7=cOvhPE7iH__7r7X6MS=e_xms7zQjc-XvZ6UA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6Zi80DUiWe5Z__+x7SzCyNTMM4g_7+oxW4Cg79njrdJQ@mail.gmail.com>

other stuff.

* gso-split no-gso-split not documented (what section do they belong in?)
* ingress/egress keywords not documented

I would like to bring out more that cake is a shaper that can also be
left unconfigured and run at line rate.

I honestly *didn't know* everybody else here wasn't using it that
way... it's my default qdisc on everything with spare cpu! dogfood it
via: sysctl -w net.core.default_qdisc=cake

"       CAKE  (Common  Applications  Kept  Enhanced) is a shaping-capable queue
        discipline which uses both AQM and FQ."

is a bit weak.

"       CAKE  uses  a  deficit-mode  shaper, which does not exhibit the initial
       burst typical of token-bucket shapers.   It  will  automatically  burst
       precisely  as  much  as required to maintain the configured throughput.
       As such, it is very straightforward to configure."

I have fiddled with the metro setting for local lans. at a gbit, the
results are "interesting" as a local qdisc,
at 100 flows, we end up with full throughput, 70k of buffering, 40k of
bql, tons of marks, bunch of drops in the
switch (which is like 192k of buffer there), and short rtts and lots
of retransmits. cwnd is capped too much.

(the sch_fq alternative is like 1.7MB in size and I haven't tried to
compare the two)

Or maybe that was a 500 flow result. Can't remember just now.

On Mon, Jul 30, 2018 at 10:23 AM Dave Taht <dave.taht@gmail.com> wrote:
>
> I would rather like the man page (one day) to include two realistic
> examples - (say a week's uptime), taken while loaded,  one example
> outbound, one example inbound, rather than the unloaded one it
> currently has and the less than massively loaded one...
>
> I loved looking over this result (at 40 users!) today.
>
> https://forum.lede-project.org/t/sqm-cake-and-piece-of-cake-qos-high-cpu-usage/17794/2



-- 

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

      reply	other threads:[~2018-07-30 17:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-29 10:05 [Cake] CAKE related iproute2 & kernel patches - keeping things in sync Kevin Darbyshire-Bryant
2018-07-29 23:42 ` Dave Taht
2018-07-30 15:07   ` Kevin Darbyshire-Bryant
2018-07-30 15:41     ` Loganaden Velvindron
2018-07-30 17:23       ` [Cake] man page bikeshed Dave Taht
2018-07-30 17:39         ` 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='CAA93jw6Q8otP7=cOvhPE7iH__7r7X6MS=e_xms7zQjc-XvZ6UA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    --cc=loganaden@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