From: Shefali Gupta <shefaligups11@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Query Regarding CAKE
Date: Wed, 24 Oct 2018 17:36:29 +0530 [thread overview]
Message-ID: <CAFp5xQ7Chmk4NKiYkabFUiPP3-EOavpEH38mAV+oCp=LEWHebg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 755 bytes --]
next reply other threads:[~2018-10-24 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 12:06 Shefali Gupta [this message]
2018-10-24 15:04 ` Dave Taht
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='CAFp5xQ7Chmk4NKiYkabFUiPP3-EOavpEH38mAV+oCp=LEWHebg@mail.gmail.com' \
--to=shefaligups11@gmail.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