Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: vignesh kannan <vignesh2496@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Doubt regarding the Linux implementation of Cake
Date: Wed, 29 Mar 2017 23:04:30 +0530	[thread overview]
Message-ID: <CAAYLTGVWot_sY5f5=nt6eoOpffdoEOn6OLhcZvCqTiJyyeiE0g@mail.gmail.com> (raw)

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

Hello,

I am Vignesh, and I am new to this mailing list. I have been going through
the Cobalt AQM algorithm implemented in the Cake framework since the last
two weeks. Here is the link :

The C file : https://github.com/dtaht/sch_cake/blob/master/cobalt.c
The header file : https://github.com/dtaht/sch_cake/blob/master/cobalt.h

I have also been following the discussions happening about Cobalt on the
Bufferbloat mailing list. So I am having problems relating the two sources
just mentioned above (the implementation and the discussion). According to
my understanding of the Codel algorithm, the count variable (which keeps
track of the number of packets dropped in the currently running dropping
state) is never really decremented iteratively.

However the Cobalt implementation reduces count iteratively (in line 234 of
the file cobalt.c) under certain circumstances and this is happening in the
function named cobalt_should_drop( ) which is called to determine if Cobalt
should drop the packet or dequeue it. It would be great if someone could
throw light on what is exactly happening in this function and also a
comprehensive explanation of Cobalt itself would be appreciated.

Thanks!

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

             reply	other threads:[~2017-03-29 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 17:34 vignesh kannan [this message]
2017-03-29 17:42 ` Jonathan Morton

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='CAAYLTGVWot_sY5f5=nt6eoOpffdoEOn6OLhcZvCqTiJyyeiE0g@mail.gmail.com' \
    --to=vignesh2496@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