From: Marco Belmonte <marco@heavenlysanctuary.com>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake anecdote from firewalla
Date: Sat, 15 Oct 2022 14:25:18 -0700 [thread overview]
Message-ID: <0a6b898a-1a4c-0134-369b-26cb6bca3b06@heavenlysanctuary.com> (raw)
In-Reply-To: <CAA93jw7RfrLMrAEzT7-_rrtOM2-7-kUy3HDfDqy+S0uydWfFsA@mail.gmail.com>
LOL! Love reading stuff like this - thanks for sharing, Dave!
On 10/14/2022 4:42 PM, Dave Taht via Cake wrote:
> "My favorite anecdote regarding CAKE is one time I started a B2 backup
> from my NAS and removed all device-side upload restrictions (which
> would normally render the internet unusable from that point on). Then
> I fired up nvidia's game streaming on the Shield to try the Tomb
> Raider demo. Long story short, an hour into the gameplay I forgot I
> was even running the backup (which was still running full tilt). That
> was the moment I knew CAKE was the hill I would die on." -
> https://www.reddit.com/r/firewalla/comments/y2257v/cake_for_smart_queues/
>
>
prev parent reply other threads:[~2022-10-15 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 23:42 Dave Taht
2022-10-15 21:25 ` Marco Belmonte [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=0a6b898a-1a4c-0134-369b-26cb6bca3b06@heavenlysanctuary.com \
--to=marco@heavenlysanctuary.com \
--cc=cake@lists.bufferbloat.net \
/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