From: Pete Heist <pete@eventide.io>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jonathan Morton <chromatix99@gmail.com>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Pre-print of Cake paper available
Date: Tue, 24 Apr 2018 10:57:47 +0200 [thread overview]
Message-ID: <CC750AA6-1502-4249-B3CE-61772F18B9BB@eventide.io> (raw)
In-Reply-To: <87r2n5802t.fsf@toke.dk>
> On Apr 24, 2018, at 10:45 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Pete Heist <pete@eventide.io> writes:
>
>>> On Apr 24, 2018, at 7:58 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>>>
>>> Turning NAT support on by default might actually be reasonable, since
>>> it doesn't really break anything if it's not needed - it just eats a
>>> bit of CPU with unnecessary conntrack lookups.
>>
>> I would be for it, if it eats say < 1% additional CPU, and preferably
>> less. I expect the impact to increase with packet rates.
>
> I'm a bit worried that the way it is implemented now, if we turn it on
> by default we risk activating conntrack even when it was otherwise
> disabled... That would be a bad side effect, so I think it's better to
> be safe and leave it for userspace to enable (which, again, we could do
> by default in sqm-scripts).
Fair enough. It sounds like cake’s configuration policy is to be more “predictable and consistent” by default than “ready to use in your home gateway” by default, which is understandable if it’s anticipated that more people will use it through some router’s UI or setup scripts than will set it up by hand from the command line…
next prev parent reply other threads:[~2018-04-24 8:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 8:39 Toke Høiland-Jørgensen
2018-04-23 9:54 ` Jonathan Morton
2018-04-23 23:01 ` Pete Heist
2018-04-23 23:31 ` Jonathan Morton
2018-04-24 5:44 ` Pete Heist
2018-04-24 5:58 ` Jonathan Morton
2018-04-24 7:15 ` Pete Heist
2018-04-24 7:56 ` Sebastian Moeller
2018-04-24 8:45 ` Toke Høiland-Jørgensen
2018-04-24 8:57 ` Pete Heist [this message]
2018-04-25 18:44 ` David Lang
2018-04-25 20:28 ` Toke Høiland-Jørgensen
2018-04-26 19:27 ` Pete Heist
2018-04-27 11:08 ` Toke Høiland-Jørgensen
2018-04-27 11:20 ` Pete Heist
2018-04-24 8:17 ` Sebastian Moeller
2018-04-24 8:47 ` Toke Høiland-Jørgensen
2018-04-24 8:50 ` Jonathan Morton
2018-04-24 9:06 ` Pete Heist
2018-04-24 9:15 ` Toke Høiland-Jørgensen
2018-04-24 9:36 ` Pete Heist
2018-04-24 9:18 ` Sebastian Moeller
2018-04-24 9:30 ` Toke Høiland-Jørgensen
2018-04-24 9:38 ` Sebastian Moeller
2018-04-24 9:44 ` Toke Høiland-Jørgensen
2018-04-24 15:08 ` John Yates
2018-04-24 8:43 ` 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=CC750AA6-1502-4249-B3CE-61772F18B9BB@eventide.io \
--to=pete@eventide.io \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=toke@toke.dk \
/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