From: Adrian Popescu <adriannnpopescu@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] cake status & forks
Date: Sat, 28 Jan 2017 13:06:45 +0200 [thread overview]
Message-ID: <CAF3M4P34XhEO_5_NCLmhyOKSLEpabru30NDssopPpDKDVxB3iA@mail.gmail.com> (raw)
Hello,
Cake has been under development for a while. It still doesn't seem to
be ready. I have some questions to ask.
LEDE uses a fork of Cake. Why does such a small project need to use a
fork to be included in another project? What's wrong with the main
repository?
Cake doesn't seem to have comments sprinkled all over the source code.
Is there any kind of documentation which describes the algorithms used
in the code? It's hard to know whether the code does the right thing
or not without comments.
Cake seems to be a lot more complicated than some of the other qdiscs.
It's harder to understand Cake's code. One such thing which isn't
documented is the logic behind the 8 way associative hash. It's hard
to tell exactly what's what because there's no explanation in the
code. Everything is spread across multiple functions without any
comments or documentation.
The lack of documentation and the Linux kernel specific code make it
quite difficult to port Cake to other operating systems. The lack of
comments and documentation makes it harder to prove the code is right.
There are no algorithms and no description of what the code does to
compare with the implementation.
What Linux kernel versions does Cake support currently? Are there any
plans to add comments to the code? Are there any plans to write
documentation on the individual discrete algorithms and constants used
in the code?
How should we compute the overhead options? How are we supposed to use
the new features without documentation?
Are there any plans for more major changes? Is the code still going to
receive major overhauls?
next reply other threads:[~2017-01-28 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 11:06 Adrian Popescu [this message]
2017-01-28 16:42 ` Dave Taht
2017-06-27 18:41 ` Adrian Popescu
2017-06-29 15:48 ` Kevin Darbyshire-Bryant
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=CAF3M4P34XhEO_5_NCLmhyOKSLEpabru30NDssopPpDKDVxB3iA@mail.gmail.com \
--to=adriannnpopescu@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