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:11:22 +0100 [thread overview]
Message-ID: <4B2F9D53-393D-44EC-8DC2-A59DFE0E6CBD@gmx.de> (raw)
In-Reply-To: <87twpaf0tq.fsf@toke.dk>
Hi Toke,
On Oct 29, 2015, at 11:04 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Sebastian Moeller <moeller0@gmx.de> writes:
>
>> This is all quite interesting and correct; the point I failed to make
>> clearly it seems, is that a 50MB limit on a 64MB router can not be called sane
>> or safe, no matter how you slice or dice it… It is one thing having cake tell me
>> that it thinks the limit I gave is to low to reach full throughput as long as it
>> accepts the given limit.
>
> Well, a solution would be to not configure your 64-MB router with a
> 100Mbit / 1000ms connection :)
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 ;)
Best Regards
Sebastian
>
> -Toke
next prev parent reply other threads:[~2015-10-29 10:11 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 [this message]
2015-10-29 10:14 ` Toke Høiland-Jørgensen
2015-10-29 10:48 ` Sebastian Moeller
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=4B2F9D53-393D-44EC-8DC2-A59DFE0E6CBD@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