Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake and nat in openwrt... on by default?
Date: Sun, 5 Apr 2020 19:56:43 +0000	[thread overview]
Message-ID: <656F3146-1B43-41DC-963C-21770747E4AC@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw5qkWxsA__+69em0BRT32-Ze42NH7VorsCW1TE_JAio3Q@mail.gmail.com>

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



> On 5 Apr 2020, at 16:22, Dave Taht <dave.taht@gmail.com> wrote:
> 
>> 
> 
> I'd still be willing to bet, then, that the majority of instances were
> not turning nat mode on, when
> they should have been.

If memory serves, at the time there was a lot of concern about cpu usage and (I felt) that every line, every potential instruction and cache hit was being scrutinised.  NAT lookup by default was deemed too much.  Cake ended up being ‘cpu heavy’ though I’ve yet to see a better combination of shaper, aqm, flow fairness, host fairness, DSCP awareness and ack filtering in one overall package, let alone one that did it in less cpu.

Cheers,

Kevin D-B

gpg: 012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-04-05 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05  4:17 Dave Taht
2020-04-05  7:57 ` Kevin Darbyshire-Bryant
2020-04-05 15:22   ` Dave Taht
2020-04-05 18:03     ` Dave Taht
2020-04-05 19:56     ` Kevin Darbyshire-Bryant [this message]
2020-04-06 10:15       ` Toke Høiland-Jørgensen

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=656F3146-1B43-41DC-963C-21770747E4AC@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --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