Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] memory
Date: Thu, 29 Oct 2015 11:48:01 +0100	[thread overview]
Message-ID: <E8C94AA7-6123-45D9-846F-A0F0C791919F@gmx.de> (raw)
In-Reply-To: <87pozyf0cu.fsf@toke.dk>

Hi Toke,


On Oct 29, 2015, at 11:14 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> Sebastian Moeller <moeller0@gmx.de> writes:
> 
>> Fair enough ;) Let’s get the soldering iron out and see whether I can
>> replace the phi with a 10Mbit one ;), mmmh, maybe I should run 10BASE5
>> and do away with all that modernist “hub” and “switch” witch craft
>> while I am at it Joking aside, I believe the issue only occurred on
>> loooong RTTs so it will only be a minor issue in real life, but still
>> it would be nice if cake would not introduce the possibility for
>> remote parties to make my router OOM/reboot ;). I might be odd, but I
>> prefer a hit in throughput to a forced reboot any day ;)
> 
> The "1 second RTT" part was a key part in that... If the RTT is set to
> 100ms (the default), you'll only get a limit of 12.5 MB…

	Yes, while trying to be funny I glossed over that part a bit (the loooong RTTs part was aiming at that), sorry. But really I am wonder what it is that makes my position that cake should expose and honor a packet limit for its queueing so controversial; I am totally happy with cake automatically selecting a good default automatically using all information it has available, like configured bandwidth and RTT, all I want to avoid the situation where cake divined something that is totally consistent within the information it has available, but is obviously wrong given additional information out of cake’s control (like total memory size or even maximum memory size the user is willing to put aside for cake). I think cake’s goal of being simple to use is commendable, but we should make sure we do not accidentally end up with cake being simplistic… (rather make the normal things easy/simple and complex/crazy things possible ;) )

Best Regards
	Sebastian


> 
> Now, there is still an issue to be resolved in "unlimited" mode. But
> that's a separate issue.
> 
> -Toke


  reply	other threads:[~2015-10-29 10:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-29  9:01 Dave Taht
2015-10-29  9:56 ` Sebastian Moeller
2015-10-29 10:04   ` Toke Høiland-Jørgensen
2015-10-29 10:11     ` Sebastian Moeller
2015-10-29 10:14       ` Toke Høiland-Jørgensen
2015-10-29 10:48         ` Sebastian Moeller [this message]
2015-10-29 11:02           ` Toke Høiland-Jørgensen
     [not found]             ` <6A01B7A9-BB31-4CF5-BE84-A54A2B860564@gmx.de>
2015-10-29 15:40               ` Toke Høiland-Jørgensen
2015-10-30  9:13                 ` Sebastian Moeller
2015-10-30 12:07                   ` Dave Taht
2015-10-30 12:21                     ` Sebastian Moeller

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=E8C94AA7-6123-45D9-846F-A0F0C791919F@gmx.de \
    --to=moeller0@gmx.de \
    --cc=cake@lists.bufferbloat.net \
    --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