From: Dave Taht <dave@taht.net>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Cake in Riverbed?
Date: Sat, 19 Jan 2019 06:17:47 -0800 [thread overview]
Message-ID: <87pnssoho4.fsf@taht.net> (raw)
In-Reply-To: <A3BA0D8B-904A-4375-9E90-42B2235ADDCD@gmail.com> (Rich Brown's message of "Wed, 16 Jan 2019 06:59:34 -0500")
https://www.bufferbloat.net/projects/codel/wiki/CakeTechnical/ needs an
update to match the final code.
Rich Brown <richb.hanover@gmail.com> writes:
> I can't remember whether I had seen this on the list or not: It appears that Riverbed is offering CAKE on its branch gateways...
>
> https://support.riverbed.com/bin/support/static/hgc5k5odj0e955sd2uk2qr4ir5/html/7h0cpt4lqflt1k1pfdpth18at9/sc_ug_html/index.html#page/sc_ug%2Fqos.html%23
>
> Rich
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2019-01-19 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 11:59 Rich Brown
2019-01-16 19:42 ` Jonathan Morton
2019-01-19 14:17 ` Dave Taht [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnssoho4.fsf@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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