Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: shefaligups11@gmail.com
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Query Regarding CAKE
Date: Wed, 24 Oct 2018 08:04:21 -0700	[thread overview]
Message-ID: <CAA93jw5OEFfpYdAV+gaT_X_hp57WwTTLig0MXeerYT+T=Oy+eQ@mail.gmail.com> (raw)
In-Reply-To: <CAFp5xQ7Chmk4NKiYkabFUiPP3-EOavpEH38mAV+oCp=LEWHebg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

Glad to hear it!

In the lwn article, cobalt was mis-identified as having something to do
with the per host fq portion of cake (which I wish we had a name for!). The
"blue" component of cake was easily at the time separated out from the
codel component, a patch and some testing were on this thread here:

https://lists.bufferbloat.net/pipermail/cake/2017-December/003167.html

At the time (in the src tree), the codel implementation in cake was
recognisably like the paper, it no longer is.


On Wed, Oct 24, 2018 at 5:06 AM Shefali Gupta <shefaligups11@gmail.com>
wrote:

> Hi all,
>
> We're working on the implementation of CAKE in ns-3, but have been facing
> an issue about finding resources on COBALT (algorithm / pseudo code). In
> the LANMAN paper on CAKE, we did not find much detail about COBALT. Can
> anyone provide us resources on COBALT.
>
> Congratulations on getting CAKE in the Linux mainline!
>
> Thanks,
> Shefali Gupta
> Jendaipou Palmei
> NITK Surathkal, India
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>


-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

[-- Attachment #2: Type: text/html, Size: 2497 bytes --]

  reply	other threads:[~2018-10-24 15:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24 12:06 Shefali Gupta
2018-10-24 15:04 ` Dave Taht [this message]
2018-10-24 18:43 ` Jonathan Morton
2018-11-19 13:55 Shefali Gupta
2018-11-19 14:22 ` Jonathan Morton
2018-11-19 16:26   ` Shefali Gupta
2018-11-19 17:59 ` Dave Taht

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='CAA93jw5OEFfpYdAV+gaT_X_hp57WwTTLig0MXeerYT+T=Oy+eQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=shefaligups11@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